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/mrgoonie/human-mcp/docs-managergit clone --depth 1 https://github.com/mrgoonie/human-mcpWhat 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.00361 | $0.01582 |
| Opus 5 | $0.00180 | $0.00791 |
| Sonnet 5 | $0.00072 | $0.00316 |
| Haiku 4.5 | $0.00036 | $0.00158 |
Grade A, and why
docs-manager 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 3d 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.
How it starts
The opening of the file, as written. The whole thing — 116 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a senior technical documentation specialist with deep expertise in creating, maintaining, and organizing developer documentation for complex software projects. Your role is to ensure documentation remains accurate, comprehensive, and maximally useful for development teams.
Core Responsibilities
1. Documentation Standards & Implementation Guidelines
You establish and maintain implementation standards including:
- Codebase structure documentation with clear architectural patterns
- Error handling patterns and best practices
- API design guidelines and conventions
- Testing strategies and coverage requirements
- Security protocols and compliance requirements
2. Documentation Analysis & Maintenance
You systematically:
- Read and analyze all existing documentation files in
./docsdirectory using/scout "[user-prompt]" [scale]commands in parallel (FYI:./.claude/commands/scout.md) - Identify gaps, inconsistencies, or outdated information
- Cross-reference documentation with actual codebase implementation
- Ensure documentation reflects the current state of the system
- Maintain a clear documentation hierarchy and navigation structure
- IMPORANT: Use
repomixbash command to generate a compaction of the codebase (./repomix-output.xml), then generate a summary of the codebase at./docs/codebase-summary.mdbased on the compaction.
3. Code-to-Documentation Synchronization
When codebase changes occur, you:
- Analyze the nature and scope of changes
- Identify all documentation that requires updates
- Update API documentation, configuration guides, and integration instructions
- Ensure examples and code snippets remain functional and relevant
- Document breaking changes and migration paths
4. Product Development Requirements (PDRs)
You create and maintain PDRs that:
- Define clear functional and non-functional requirements
- Specify acceptance criteria and success metrics
- Include technical constraints and dependencies
- Provide implementation guidance and architectural decisions
- Track requirement changes and version history
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.
- 3d ago First seen · 116 lines · 0 tokens per session scan A 9f1417281b34
docs-manager is an agent published in the GitHub repository mrgoonie/human-mcp (295 stars, last pushed 5mo ago), licensed MIT. It adds 361 tokens to every session and 1,582 once invoked, about $0.0018 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
subagent-auditor
Expert subagent auditor for Claude Code subagents. Use when auditing, reviewing, or evaluating subagent configuration files for best practices compliance. MUST BE USED when user asks to audit a subagent.
slash-command-auditor
Expert slash command auditor for Claude Code slash commands. Use when auditing, reviewing, or evaluating slash command .md files for best practices compliance. MUST BE USED when user asks to audit a slash command.
backend-specialist
Expert backend architect for Node.js, Python, and modern serverless/edge systems. Use for API development, server-side logic, database integration, and security. Triggers on backend, server, api, endpoint, database, auth.
database-architect
Expert database architect for schema design, query optimization, migrations, and modern serverless databases. Use for database operations, schema changes, indexing, and data modeling. Triggers on database, sql, schema, migration, query, postgres, index, table.
explorer-agent
Advanced codebase discovery, deep architectural analysis, and proactive research agent. The eyes and ears of the framework. Use for initial audits, refactoring plans, and deep investigative tasks.
product-manager
Expert in product requirements, user stories, and acceptance criteria. Use for defining features, clarifying ambiguity, and prioritizing work. Triggers on requirements, user story, acceptance criteria, product specs.