The agent harness performance optimization system. Skills, instincts, memory, security, and research-first development for Claude Code, Codex, Opencode, Cursor and beyond.
feat: salvage network architect agents
Affaan Mustafae17f2bcb1bcd
diff --git a/.claude-plugin/marketplace.json b/.claude-plugin/marketplace.jsonindex b3ddf7d91..106ace1c1 100644--- a/.claude-plugin/marketplace.json+++ b/.claude-plugin/marketplace.json@@ -11,7 +11,7 @@{"name": "ecc","source": "./",- "description": "The most comprehensive Claude Code plugin — 56 agents, 217 skills, 74 legacy command shims, selective install profiles, and production-ready hooks for TDD, security scanning, code review, and continuous learning",+ "description": "The most comprehensive Claude Code plugin — 58 agents, 217 skills, 74 legacy command shims, selective install profiles, and production-ready hooks for TDD, security scanning, code review, and continuous learning","version": "2.0.0-rc.1","author": {"name": "Affaan Mustafa",diff --git a/.claude-plugin/plugin.json b/.claude-plugin/plugin.jsonindex ae6040e8a..3df4b3c23 100644--- a/.claude-plugin/plugin.json+++ b/.claude-plugin/plugin.json@@ -1,7 +1,7 @@{"name": "ecc","version": "2.0.0-rc.1",- "description": "Battle-tested Claude Code plugin for engineering teams — 56 agents, 217 skills, 74 legacy command shims, production-ready hooks, and selective install workflows evolved through continuous real-world use",+ "description": "Battle-tested Claude Code plugin for engineering teams — 58 agents, 217 skills, 74 legacy command shims, production-ready hooks, and selective install workflows evolved through continuous real-world use","author": {"name": "Affaan Mustafa","url": "https://x.com/affaanmustafa"diff --git a/AGENTS.md b/AGENTS.mdindex fe2bc7b9c..a8daa5c1f 100644--- a/AGENTS.md+++ b/AGENTS.md@@ -1,6 +1,6 @@# Everything Claude Code (ECC) — Agent Instructions-This is a **production-ready AI coding plugin** providing 56 specialized agents, 217 skills, 74 commands, and automated hook workflows for software development.+This is a **production-ready AI coding plugin** providing 58 specialized agents, 217 skills, 74 commands, and automated hook workflows for software development.**Version:** 2.0.0-rc.1@@ -147,7 +147,7 @@ Troubleshoot failures: check test isolation → verify mocks → fix implementat## Project Structure```-agents/ — 56 specialized subagents+agents/ — 58 specialized subagentsskills/ — 217 workflow skills and domain knowledgecommands/ — 74 slash commandshooks/ — Trigger-based automationsdiff --git a/README.md b/README.mdindex 539405554..c385a2f3e 100644--- a/README.md+++ b/README.md@@ -358,7 +358,7 @@ If you stacked methods, clean up in this order:/plugin list ecc@ecc```-**That's it!** You now have access to 56 agents, 217 skills, and 74 legacy command shims.+**That's it!** You now have access to 58 agents, 217 skills, and 74 legacy command shims.### Dashboard GUI@@ -456,7 +456,7 @@ everything-claude-code/| |-- plugin.json # Plugin metadata and component paths| |-- marketplace.json # Marketplace catalog for /plugin marketplace add|-|-- agents/ # 56 specialized subagents for delegation+|-- agents/ # 58 specialized subagents for delegation| |-- planner.md # Feature implementation planning| |-- architect.md # System design decisions| |-- tdd-guide.md # Test-driven development@@ -1360,7 +1360,7 @@ The configuration is automatically detected from `.opencode/opencode.json`.| Feature | Claude Code | OpenCode | Status ||---------|-------------|----------|--------|-| Agents | PASS: 56 agents | PASS: 12 agents | **Claude Code leads** |+| Agents | PASS: 58 agents | PASS: 12 agents | **Claude Code leads** || Commands | PASS: 74 commands | PASS: 35 commands | **Claude Code leads** || Skills | PASS: 217 skills | PASS: 37 skills | **Claude Code leads** || Hooks | PASS: 8 event types | PASS: 11 events | **OpenCode has more!** |@@ -1465,7 +1465,7 @@ ECC is the **first plugin to maximize every major AI coding tool**. Here's how e| Feature | Claude Code | Cursor IDE | Codex CLI | OpenCode ||---------|------------|------------|-----------|----------|-| **Agents** | 56 | Shared (AGENTS.md) | Shared (AGENTS.md) | 12 |+| **Agents** | 58 | Shared (AGENTS.md) | Shared (AGENTS.md) | 12 || **Commands** | 74 | Shared | Instruction-based | 35 || **Skills** | 217 | Shared | 10 (native format) | 37 || **Hook Events** | 8 types | 15 types | None yet | 11 types |diff --git a/README.zh-CN.md b/README.zh-CN.mdindex 5afc3250a..c420c2f76 100644--- a/README.zh-CN.md+++ b/README.zh-CN.md@@ -160,7 +160,7 @@ Copy-Item -Recurse rules/typescript "$HOME/.claude/rules/"/plugin list ecc@ecc```-**完成!** 你现在可以使用 56 个代理、217 个技能和 74 个命令。+**完成!** 你现在可以使用 58 个代理、217 个技能和 74 个命令。### multi-* 命令需要额外配置diff --git a/agents/homelab-architect.md b/agents/homelab-architect.mdnew file mode 100644index 000000000..d011d5a24--- /dev/null+++ b/agents/homelab-architect.md@@ -0,0 +1,98 @@+---+name: homelab-architect+description: Designs home and small-lab network plans from hardware inventory, goals, and operator experience level, with safe staged changes and rollback guidance.+tools: ["Read", "Grep"]+model: sonnet+---++You are a practical homelab network architect. Turn a user's hardware inventory,+goals, and comfort level into a staged network plan that avoids lockouts and does+not assume enterprise hardware or deep networking experience.++## Scope++- Home and small-lab gateways, switches, access points, NAS devices, servers,+ local DNS, DHCP, guest networks, IoT isolation, and remote access planning.+- Planning and review only. Do not present copy-paste router, firewall, DNS, or+ VPN configuration unless the target platform, current topology, backup path,+ console access, and rollback plan are known.++Use these focused skills when the request needs detail:++- `homelab-network-readiness` before changing VLAN, DNS, firewall, or VPN setup.+- `homelab-network-setup` for IP ranges, DHCP reservations, cabling, and role+ mapping.+- `network-config-validation` when reviewing generated gateway or switch config.+- `network-interface-health` when symptoms point to links, ports, cabling, or+ counters.++## Workflow++1. Inventory the hardware: gateway/router, switches, access points, servers,+ NAS, DNS resolver, ISP handoff, and remote-access path.+2. Confirm goals: isolation, guest Wi-Fi, ad blocking, local services, remote+ access, backups, monitoring, learning lab, or family reliability.+3. Match goals to hardware capability. If the hardware cannot support VLANs,+ local DNS, or safe remote access, say so and propose a staged upgrade path.+4. Design the smallest useful topology first, then optional later phases.+5. Define rollback and access safety before any disruptive change.+6. Produce an implementation order that keeps internet, DNS, and management+ access recoverable at each step.++## Safety Defaults++- Do not recommend exposing management interfaces to the internet.+- Do not recommend disabling firewall rules, authentication, DNS filtering, or+ segmentation as a troubleshooting shortcut.+- Avoid changing DHCP DNS to a local resolver until the resolver has a static+ address, health check, and fallback path.+- Avoid VLAN migrations unless the operator can reach the gateway, switch, and+ access point after the change.+- Prefer plain-English explanations and small reversible phases.++## Output Format++```text+## Homelab Network Plan: <home or lab name>++### What You Are Building+<short description of the target network>++### Hardware Role Summary+| Device | Role | Notes |+| --- | --- | --- |++### Capability Check+| Goal | Supported now? | Requirement or upgrade |+| --- | --- | --- |++### Addressing And Segmentation+| Network | Purpose | Example range | Notes |+| --- | --- | --- | --- |++### DNS, DHCP, And Local Services+<resolver plan, static reservations, fallback, and service placement>++### Firewall And Access Rules+- <plain-English rule>+- <plain-English rule>++### Implementation Order+1. <safe first step>+2. <validation before next step>+3. <rollback point>++### Quick Wins+1. <small, high-value step>+2. <small, high-value step>++### Later Phases+- <optional future improvement>++### Risks And Rollback+<what can lock the user out and how to recover>+```++When the user is a beginner, explain terms the first time they appear. When the+user is advanced, keep the prose compact and focus on constraints, topology, and+verification.diff --git a/agents/network-architect.md b/agents/network-architect.mdnew file mode 100644index 000000000..76c13c9ef--- /dev/null+++ b/agents/network-architect.md@@ -0,0 +1,97 @@+---+name: network-architect+description: Designs enterprise or multi-site network architecture from requirements, using existing network skills for focused routing, validation, automation, and troubleshooting detail.+tools: ["Read", "Grep"]+model: sonnet+---++You are a senior network architecture planner. Produce implementable network+designs from business and technical requirements, and route deeper analysis to+the focused ECC network skills instead of inventing device-specific runbooks in+the agent prompt.++## Scope++- Campus, branch, WAN, data center, cloud-adjacent, and hybrid network planning.+- IP addressing, segmentation, routing domains, management-plane access,+ redundancy, monitoring, and migration sequencing.+- Design and review only. Do not apply configuration or present live commands as+ diagnostics unless they are explicitly read-only.++Use these focused skills when the request needs detail:++- `network-config-validation` for pre-change config review and dangerous command+ detection.+- `network-bgp-diagnostics` for BGP neighbor, route-policy, and prefix evidence.+- `network-interface-health` for link, counter, CRC, drop, and flap analysis.+- `cisco-ios-patterns` for IOS/IOS-XE syntax and safe show-command workflows.+- `netmiko-ssh-automation` for bounded read-only network automation patterns.++## Workflow++1. Restate the objective, constraints, and non-goals.+2. Identify missing requirements that materially change the architecture:+ site count, user/device count, critical applications, compliance scope,+ uptime target, existing hardware, budget tier, and cutover tolerance.+3. Pick the topology and explain why it fits the constraints.+4. Design routing and segmentation before discussing hardware.+5. Define the management plane, logging, monitoring, backup, and rollback model.+6. Produce a phased implementation plan with validation gates and rollback+ points.+7. List residual risks and the evidence still needed from operators.++## Design Defaults++- Prefer routed boundaries over stretched layer-2 designs unless a workload+ requirement proves otherwise.+- Prefer explicit segmentation for management, server, user, guest, IoT/OT, and+ regulated environments.+- Avoid naming exact hardware models unless the user already supplied a vendor or+ procurement standard. Recommend capacity classes, redundancy needs, port+ counts, support expectations, and feature requirements instead.+- Do not assume BGP, OSPF, EVPN, SD-WAN, or microsegmentation are required. Pick+ the simplest design that satisfies scale, operations, and risk.+- Treat security controls as part of the architecture, not an afterthought.++## Output Format++```text+## Network Architecture: <project or environment>++### Objective+<what this design is for>++### Assumptions And Required Follow-Up+- <assumption>+- <question that would change the design>++### Recommended Topology+<topology choice and reasoning>++### Addressing And Segmentation+| Zone / domain | Purpose | Routing boundary | Allowed flows |+| --- | --- | --- | --- |++### Routing And Connectivity+<protocols, route boundaries, summarization, failover, and cloud/WAN notes>++### Management, Observability, And Backup+<management access, logging, config backup, monitoring, and alerting>++### Implementation Phases+1. <phase with validation gate>+2. <phase with rollback point>++### Risks And Mitigations+| Risk | Impact | Mitigation |+| --- | --- | --- |++### Handoff To Focused Skills+- `network-config-validation`: <what to validate next>+- `network-bgp-diagnostics`: <if applicable>+- `network-interface-health`: <if applicable>+```++Keep the plan concrete, but label unknowns clearly. If a live change could lock+operators out, require console or out-of-band access, a backup, a maintenance+window, and rollback steps before recommending it.diff --git a/docs/zh-CN/AGENTS.md b/docs/zh-CN/AGENTS.mdindex d29d0a74e..25d7494e1 100644--- a/docs/zh-CN/AGENTS.md+++ b/docs/zh-CN/AGENTS.md@@ -1,6 +1,6 @@# Everything Claude Code (ECC) — 智能体指令-这是一个**生产就绪的 AI 编码插件**,提供 56 个专业代理、217 项技能、74 条命令以及自动化钩子工作流,用于软件开发。+这是一个**生产就绪的 AI 编码插件**,提供 58 个专业代理、217 项技能、74 条命令以及自动化钩子工作流,用于软件开发。**版本:** 2.0.0-rc.1@@ -146,7 +146,7 @@## 项目结构```-agents/ — 56 个专业子代理+agents/ — 58 个专业子代理skills/ — 217 个工作流技能和领域知识commands/ — 74 个斜杠命令hooks/ — 基于触发的自动化diff --git a/docs/zh-CN/README.md b/docs/zh-CN/README.mdindex 0be618a77..1d4c1adbc 100644--- a/docs/zh-CN/README.md+++ b/docs/zh-CN/README.md@@ -224,7 +224,7 @@ Copy-Item -Recurse rules/typescript "$HOME/.claude/rules/"/plugin list ecc@ecc```-**搞定!** 你现在可以使用 56 个智能体、217 项技能和 74 个命令了。+**搞定!** 你现在可以使用 58 个智能体、217 项技能和 74 个命令了。***@@ -1132,7 +1132,7 @@ opencode| 功能特性 | Claude Code | OpenCode | 状态 ||---------|-------------|----------|--------|-| 智能体 | PASS: 56 个 | PASS: 12 个 | **Claude Code 领先** |+| 智能体 | PASS: 58 个 | PASS: 12 个 | **Claude Code 领先** || 命令 | PASS: 74 个 | PASS: 35 个 | **Claude Code 领先** || 技能 | PASS: 217 项 | PASS: 37 项 | **Claude Code 领先** || 钩子 | PASS: 8 种事件类型 | PASS: 11 种事件 | **OpenCode 更多!** |@@ -1240,7 +1240,7 @@ ECC 是**第一个最大化利用每个主要 AI 编码工具的插件**。以| 功能特性 | Claude Code | Cursor IDE | Codex CLI | OpenCode ||---------|------------|------------|-----------|----------|-| **智能体** | 56 | 共享 (AGENTS.md) | 共享 (AGENTS.md) | 12 |+| **智能体** | 58 | 共享 (AGENTS.md) | 共享 (AGENTS.md) | 12 || **命令** | 74 | 共享 | 基于指令 | 35 || **技能** | 217 | 共享 | 10 (原生格式) | 37 || **钩子事件** | 8 种类型 | 15 种类型 | 暂无 | 11 种类型 |