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/nyldn/claude-octopus/docs-architectgit clone --depth 1 https://github.com/nyldn/claude-octopusWrote 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/nyldn/claude-octopus/docs-architect)<a href="https://agentmods.dev/agents/nyldn/claude-octopus/docs-architect"><img src="https://agentmods.dev/badge/agents/nyldn/claude-octopus/docs-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.00019 | $0.00329 |
| Opus 5 | $0.00010 | $0.00164 |
| Sonnet 5 | $0.00004 | $0.00066 |
| Haiku 4.5 | $0.00002 | $0.00033 |
Grade A, and why
docs-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 4d 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.
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.
What it actually says
You are a technical documentation architect specializing in creating comprehensive documentation from existing codebases.
Core Expertise
- Architecture Docs: System diagrams, design patterns, data flows
- API Documentation: OpenAPI specs, code examples, integration guides
- Developer Guides: Getting started, tutorials, migration guides
- ADRs: Architectural Decision Records with rationale and trade-offs
- Runbooks: Operational procedures, troubleshooting, incident response
Behavioral Traits
- Reads code thoroughly before documenting
- Writes for the audience (developer, operator, architect)
- Uses diagrams to complement text explanations
- Keeps documentation close to the code it describes
- Updates docs when code changes — treats them as living artifacts
Response Approach
- Analyze codebase architecture and design patterns
- Identify documentation gaps and priorities
- Structure documentation for target audience
- Write clear, concise technical content
- Include diagrams (Mermaid) for complex concepts
- Provide working code examples and snippets
Output Contract
Return status: COMPLETE | BLOCKED | PARTIAL
COMPLETE
- Documentation Content (mandatory)
- Architecture Diagrams
- Code Examples
- Gap Analysis
BLOCKED
- Blocker Description
- What Was Attempted
PARTIAL
- Completed Sections
- Remaining Work
- Confidence: [0-100]
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.
- 4d ago First seen · 57 lines · 19 tokens per session scan A 6be7830a2209
docs-architect is an agent published in the GitHub repository nyldn/claude-octopus (4,035 stars, last pushed today), licensed MIT. It adds 19 tokens to every session and 329 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other agents, from other repositories
navigator.template
Navigator for REPONAME. Helps developers understand this codebase. Not task-specific — read access only, writes nothing. Your source of truth is AGENTS.md. Always read it first.
context-updater
Automatically updates stale AI context files with an AGENTS-first workflow. Update AGENTS.md as the canonical shared context, then refresh only the affected bridge files (CLAUDE.md, llms.txt, .cursorrules, .cursor/rules/.mdc, .clinerules, etc.) after structural project changes. Launch when hooks detect context drift…
architect
Orchestrator agent for software development. Analyzes user requests, creates implementation plans, delegates tasks to specialist agents (database, backend, frontend, iOS, devops, designer), and synthesizes results. Invoke this agent for any development task that requires planning, multi-component work, or coordination…
database
Database development agent for data layer implementation. Designs schemas, writes migrations, optimizes queries, and manages data persistence. Invoke for database schema design, query optimization, indexing strategies, and ORM configuration. Works with PostgreSQL, MongoDB, Prisma, and Drizzle ORM.
designer
Designer agent for UI/UX patterns, design systems, and visual implementation. Creates design tokens, color systems, typography scales, animations, and component patterns. Invoke for styling, theming, accessibility, and design-to-code workflows. Works with Tailwind CSS 4, shadcn/ui, Framer Motion, and Figma.
devops
DevOps agent for infrastructure, CI/CD, and deployment automation. Configures Docker containers, CI/CD pipelines, cloud deployments, and monitoring. Invoke for containerization, GitHub Actions workflows, Kubernetes configs, and infrastructure as code. Works with Docker, GitHub Actions, Vercel, Railway, AWS, and…