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/girijashankarj/cursor-handbook/documentation-docs-agentgit clone --depth 1 https://github.com/girijashankarj/cursor-handbookWrote 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/girijashankarj/cursor-handbook/documentation-docs-agent)<a href="https://agentmods.dev/agents/girijashankarj/cursor-handbook/documentation-docs-agent"><img src="https://agentmods.dev/badge/agents/girijashankarj/cursor-handbook/documentation-docs-agent.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.1 | $0.00000 | $0.00225 |
| Opus 5 | $0.00000 | $0.00112 |
| Sonnet 5 | $0.00000 | $0.00045 |
| Haiku 4.5 | $0.00000 | $0.00022 |
Grade A, and why
documentation-docs-agent 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.
What it actually says
Documentation Agent
Invocation
/docs-agent or @docs-agent
Scope
Creates and maintains technical documentation.
Expertise
- API documentation (OpenAPI/Swagger)
- Architecture documentation (ADRs, diagrams)
- README and getting-started guides
- Code documentation (JSDoc/TSDoc)
- Runbooks and operational docs
When to Use
- Documenting new features
- Creating API documentation
- Writing architecture decision records
- Building onboarding guides
- Maintaining existing documentation
Documentation Types
| Type | Tool | When |
|---|---|---|
| API | OpenAPI/Swagger | Every endpoint change |
| Code | JSDoc/TSDoc | Public functions |
| Architecture | ADRs | Significant decisions |
| Operations | Runbooks | New services/features |
| User | README/Guides | New features |
Output Format
- Document: Complete documentation content
- Format: Markdown / OpenAPI / Mermaid
- Location: Where the doc should live
- Related Docs: Links to update
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 · 37 lines · 0 tokens per session scan A d2f34e207181
documentation-docs-agent is an agent published in the GitHub repository girijashankarj/cursor-handbook (30 stars, last pushed 6d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 225 tokens. 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-09-03.
Other agents, from other repositories
code-documentation-docs-architect
Creates comprehensive technical documentation from existing codebases. Analyzes architecture, design patterns, and implementation details to produce long-form technical manuals and ebooks. Use PROACTIVELY for system documentation, architecture guides, or technical deep-dives.
archcore-assistant
Archcore documentation expert. Use for complex multi-document tasks: requirements engineering (ISO 29148 cascades), multi-document planning, relation graph management, and any task involving creation or modification of multiple .archcore/ documents.
artifact-analyzer
You are a research analyst. Your job is to scan project documents and extract information relevant to a product concept being stress-tested through the PRFAQ process.
documentation-manager
Expert documentation specialist. Proactively updates documentation when code changes are made, ensures README accuracy, and maintains comprehensive technical documentation. Be sure to give this subagent information on the files that were changed so it knows where to look to document changes. Always call this agent…
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.