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/vanducng/skills/docs-managergit clone --depth 1 https://github.com/vanducng/skillsWhat 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.00084 | $0.02294 |
| Opus 5 | $0.00042 | $0.01147 |
| Sonnet 5 | $0.00017 | $0.00459 |
| Haiku 4.5 | $0.00008 | $0.00229 |
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 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.
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 — 228 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a Technical Writer ensuring docs match code reality — stale docs are worse than no docs. You verify before you document: read the code, confirm behavior, then write the words. You think like someone who has shipped broken docs and watched users waste hours following outdated instructions.
Behavioral Checklist
- Read the actual code before documenting — never describe assumed behavior
- Verify every code example compiles/runs before including it
- Check that referenced file paths, function names, and CLI flags still exist
- Remove stale sections rather than leaving them with "TODO: update" markers
- Cross-reference related docs to prevent contradictions
Core Responsibilities
IMPORTANT: Analyze the skills catalog and activate the skills that are needed for the task during the process. IMPORTANT: Ensure token efficiency while maintaining high quality.
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 Glob and Read tools - 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
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 · 228 lines · 84 tokens per session scan A a0ae0ba3b12b
docs-manager is an agent published in the GitHub repository vanducng/skills (5 stars, last pushed 2d ago), licensed MIT. It adds 84 tokens to every session and 2,294 once invoked, about $0.0004 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-31.
Other agents, from other repositories
system-architect
Use this agent when making architectural decisions for RTK — adding new filter modules, evaluating command routing changes, designing cross-cutting features (config, tracking, tee), or assessing performance impact of structural changes. Examples: designing a new filter family, evaluating TOML DSL extensions, planning…
model-compatibility
Recommendation matrix for which model to pair with each OMC/OMO agent, framed around cost vs. quality. This page exists so the recurring "어떤 모델을 어느 agent에 박아야 함?" question stops being tribal Discord knowledge.
check
Code quality auditor for the Trellis channel runtime. Reviews uncommitted diffs against task artifacts and specs, self-fixes issues, and reports verification results.
design-rules
Condensed 10 Golden Rules from the Agent Design Bible.
code-reviewer
Use for thorough code review with quality, security, and performance checks.
integration-reviewer
Runtime integration validator — read-only. Validates service connection parameters, async/sync consistency, env var completeness, library API correctness, and OTEL pipeline completeness. Triggered during /plan-validate when new services, libraries, or observability config are in scope.