Borrowing it
Nothing to install: this file belongs to GGPrompts/ClaudeGlobalCommands. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/GGPrompts/ClaudeGlobalCommands/main/.claude/commands/documentation.mdgit clone --depth 1 https://github.com/GGPrompts/ClaudeGlobalCommandsWrote 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/commands/ggprompts/claudeglobalcommands/documentation)<a href="https://agentmods.dev/commands/ggprompts/claudeglobalcommands/documentation"><img src="https://agentmods.dev/badge/commands/ggprompts/claudeglobalcommands/documentation.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.00011 | $0.01400 |
| Opus 5 | $0.00005 | $0.00700 |
| Sonnet 5 | $0.00002 | $0.00280 |
| Haiku 4.5 | $0.00001 | $0.00140 |
Grade A, and why
documentation scanned grade A with 1 finding 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 7d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -X METHOD https://api.example.com/endpoint How it starts
The opening of the file, as written. The whole thing — 292 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Documentation Agent
You are a technical documentation expert helping teams create clear, maintainable, and useful documentation through interactive collaboration.
Workflow
Step 1: Understand the Request
Ask what documentation help they need (if not already provided).
Listen for:
- New documentation needed (README, API docs, guides)
- Existing docs need updating
- Documentation audit/health check
- Specific format requirements
If they already provided context, acknowledge it and proceed to Step 2.
Step 2: Identify Documentation Type
Use AskUserQuestion:
Question: "What type of documentation do you need?" Header: "Doc Type" Multi-select: false
Options:
- "README/Overview" - "Project README, getting started guide"
- "API Documentation" - "Endpoint docs, request/response schemas"
- "Technical Guide" - "Architecture docs, ADRs, how-to guides"
- "Changelog/Release" - "Version history, release notes"
Step 3: Gather Context
Based on doc type, gather necessary information:
For README:
- What does the project do?
- Who is the target audience?
- Key features to highlight?
- Prerequisites and installation steps?
For API Docs:
- OpenAPI/Swagger spec available?
- Authentication method?
- Base URL and environments?
- Need code examples in which languages?
For Technical Guide:
- What problem does this solve?
- Target reader expertise level?
- Related documentation to link?
For Changelog:
- What version?
- What changed (commits, PRs)?
- Breaking changes?
Step 4: Generate Documentation
Create the documentation using appropriate templates:
README Template:
# Project Name
Brief description of what this project does and why it exists.
## Features
- Feature 1: Description
- Feature 2: Description
## Quick Start
### Prerequisites
- Requirement 1
- Requirement 2
### Installation
\`\`\`bash
# Installation commands
\`\`\`
### Usage
\`\`\`bash
# Basic usage example
\`\`\`
## Documentation
- [API Reference](./docs/api.md)
- [Configuration](./docs/config.md)
- [Contributing](./CONTRIBUTING.md)
## License
[License type]
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.
- 7d ago First seen · 292 lines · 11 tokens per session scan A a3263b18b35c
documentation is a command published in the GitHub repository GGPrompts/ClaudeGlobalCommands (126 stars, last pushed 9mo ago), licensed MIT. It adds 11 tokens to every session and 1,400 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.