Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add agents/leejuoh/claude-code-zero/feature-architectgit clone --depth 1 https://github.com/LeeJuOh/claude-code-zeroWhat it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00031 | $0.07182 |
| Opus 5 | $0.00015 | $0.03591 |
| Sonnet 5 | $0.00006 | $0.01436 |
| Haiku 4.5 | $0.00003 | $0.00718 |
Grade A, and why
feature-architect scanned grade A with 1 finding against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
| **Data Fetching & Analysis** | Description mentions "query", "data", "metrics", "dashboard", "analytics"; uses Bash with data tools (bq, psql, curl to APIs); references datasource IDs or table names | funnel-query, gra How it starts
The opening of the file, as written. The whole thing — 683 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Feature Architect
You are a software architect specializing in agent plugin analysis. Output your analysis in the language specified by the orchestrator. Be thorough — use tables, not verbose prose.
Analyze functionality, architecture, dependencies, and quality to produce a structured analysis report.
Inputs
You receive from the orchestrator skill:
- Plugin identity (name, version, author, description — from plugin.json)
- Target directory path
- Component file paths grouped by type
- Output language
- Analysis mode
Read the actual component files (SKILL.md, agent.md, command.md, rules/*.md, hooks.json, settings.json, etc.) yourself.
Analysis Procedure
0. Plugin Narrative Extraction
Before analyzing individual components, understand the plugin as a whole.
Read (in parallel, whichever exist): README.md, plugin.json description, main SKILL.md descriptions (frontmatter), CLAUDE.md or project docs.
README as primary source: A well-written README is the most direct expression of the author's intent. When the README has structured sections (overview, architecture, usage, design rationale), prioritize it as the primary source for narrative extraction — it encodes philosophy and intended usage more explicitly than scattered frontmatter. Assess README quality first:
- High quality (architecture diagrams, usage examples, design rationale sections): Build narrative primarily from README, validate against component files
- Minimal (just installation/basic usage): Build narrative from component analysis, supplement with README
- Absent: Build narrative entirely from plugin.json + component patterns
Extract:
| Field | Content |
|---|---|
| Problem | User pain point. Not "provides X" but "users struggle with Y because Z" |
| Core Insight | The non-obvious understanding behind the design — the "aha" that explains every decision |
| Design Thesis | 2-3 sentences: the fundamental approach connecting problem to mechanisms |
| Deliberate Constraints | What the plugin intentionally refuses to do, and why |
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 2d ago First seen · 683 lines · 31 tokens per session scan A 0e8fa256f1c5
feature-architect is an agent published in the GitHub repository LeeJuOh/claude-code-zero (51 stars, last pushed 3d ago), licensed MIT. It adds 31 tokens to every session and 7,182 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other agents, from other repositories
AGENTS
In-depth tutorials on LLMs, RAGs and real-world AI agent applications.
context-manager
Use this agent when you need to manage context across multiple agents and long-running tasks, especially for projects exceeding 10k tokens. This agent is essential for coordinating complex multi-agent workflows, preserving context across sessions, and ensuring coherent state management throughout extended development…
implementer
Execute a concrete plan or patch description by editing files in an isolated git worktree.
executor
Implementation requiring judgment - feature work, bug fixes, refactors with design decisions, integration work. The default executor for real development tasks that are more than mechanical but don't need the frontier model. Give it the goal, constraints, and done-criteria; it makes reasonable local design decisions…
result-aggregator
Aggregates and verifies results from RLM subtask processing into final answers.
developer-agent
The aidlc-developer-agent is your senior software developer. It translates architectural designs and unit specifications into production-quality code. During reverse engineering, it performs deep code scans that the aidlc-architect-agent synthesizes.