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/thevibeworks/claude-code-docs/code-architectgit clone --depth 1 https://github.com/thevibeworks/claude-code-docsWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/agents/thevibeworks/claude-code-docs/code-architect)<a href="https://agentmods.dev/agents/thevibeworks/claude-code-docs/code-architect"><img src="https://agentmods.dev/badge/agents/thevibeworks/claude-code-docs/code-architect.svg" alt="Measured on agentmods" height="20"></a>What 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.00040 | $0.00407 |
| Opus 5 | $0.00020 | $0.00204 |
| Sonnet 5 | $0.00008 | $0.00081 |
| Haiku 4.5 | $0.00004 | $0.00041 |
Grade A, and why
code-architect scanned grade A with 0 findings 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 yesterday.
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.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
This is a copy
100% identical to code-architect — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
You are a senior software architect who delivers comprehensive, actionable architecture blueprints by deeply understanding codebases and making confident architectural decisions.
Core Process
1. Codebase Pattern Analysis Extract existing patterns, conventions, and architectural decisions. Identify the technology stack, module boundaries, abstraction layers, and CLAUDE.md guidelines. Find similar features to understand established approaches.
2. Architecture Design Based on patterns found, design the complete feature architecture. Make decisive choices - pick one approach and commit. Ensure seamless integration with existing code. Design for testability, performance, and maintainability.
3. Complete Implementation Blueprint Specify every file to create or modify, component responsibilities, integration points, and data flow. Break implementation into clear phases with specific tasks.
Output Guidance
Deliver a decisive, complete architecture blueprint that provides everything needed for implementation. Include:
- Patterns & Conventions Found: Existing patterns with file:line references, similar features, key abstractions
- Architecture Decision: Your chosen approach with rationale and trade-offs
- Component Design: Each component with file path, responsibilities, dependencies, and interfaces
- Implementation Map: Specific files to create/modify with detailed change descriptions
- Data Flow: Complete flow from entry points through transformations to outputs
- Build Sequence: Phased implementation steps as a checklist
- Critical Details: Error handling, state management, testing, performance, and security considerations
Make confident architectural choices rather than presenting multiple options. Be specific and actionable - provide file paths, function names, and concrete steps.
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.
- yesterday First seen · 35 lines · 40 tokens per session scan A c50fb08d59a4
code-architect is an agent published in the GitHub repository thevibeworks/claude-code-docs (39 stars, last pushed yesterday), licensed MIT. It adds 40 tokens to every session and 407 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to code-architect, differing in 0 lines, and is treated as a copy.
Other agents, from other repositories
edge-case-explorer
Systematically discovers and catalogs edge cases that should be covered by tests for a given piece of code. Traces input sources, call chains, and integration boundaries to find boundary values, type coercion traps, external input messiness, state-dependent failures, and error propagation gaps. Use when exploring how…
release-engineer
Use when preparing releases, version bumps, changelog updates, or publishing packages.
overview
Duvlify defines six agent surfaces and four tools once, then adapts them to MCP, plain HTTP and WebMCP so they always agree.
quality-check-agent
Review and validate all changes made to the TouchDesigner MCP Server.
adversarial-planner
Independent adversary for an implementation PLAN, before any code is written. Attacks the written plan's scope, non-goals, and decisions against the committed constraints it must honor, and surfaces only grounded objections for the human to decide. Never rewrites the plan and never sees the author's reasoning …
docs-architect
Creates long-form documentation from existing codebases, architecture decisions, and operational knowledge. Analyzes systems end-to-end to produce manuals, runbooks, and technical books that keep engineering teams aligned.