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 commands/acaprino/daodan/docs-maintaingit clone --depth 1 https://github.com/acaprino/daodanWhat 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.00112 | $0.02588 |
| Opus 5 | $0.00056 | $0.01294 |
| Sonnet 5 | $0.00022 | $0.00518 |
| Haiku 4.5 | $0.00011 | $0.00259 |
Grade A, and why
docs-maintain 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 — 200 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Maintain Documentation
Use the documentation-engineer agent to audit and refactor existing documentation:
$ARGUMENTS
This command provides a comprehensive documentation management workflow:
What This Does
-
Audit Phase - Inventories all existing documentation and runs a per-dimension drift check against the actual codebase. For each dimension the audit reports added / removed / renamed / retyped items, not just generic "outdated content". See "Per-Dimension Drift Checks" below for the full matrix.
-
Planning Phase - Creates a refactoring plan to fix identified issues:
- Merge duplicate content
- Update outdated sections with surgical Edits (per dimension)
- Link or archive orphaned pages
- Fix broken references
- Add missing sections for undocumented dimensions
-
Interactive Decision - Asks if you want to execute the refactoring plan
-
Execution Phase (optional) - Applies refactoring with your approval:
- Reorganizes documentation structure
- Merges and consolidates content
- Updates references and links
- Verifies no content was lost
When to Use
Use this command when you need to:
- Perform quarterly documentation health checks
- Clean up docs after major codebase refactoring
- Fix scattered or duplicated documentation
- Prepare documentation before onboarding new team members
- Identify gaps in API documentation coverage
- Ensure documentation matches current implementation
Example Interactive Flow
Audit-only workflow (report without changes):
You: /docs-maintain --audit-only
Agent: I've inventoried your documentation. Found:
- 3 duplicate documentation files
- 5 outdated sections that don't match code
- 2 orphaned pages
- 1 broken link
[Detailed audit report provided]
Full refactoring workflow (audit -> plan -> execute):
You: /docs-maintain
Agent: I've inventoried your documentation. Found:
- 3 duplicate documentation files
- 5 outdated sections that don't match code
- 2 orphaned pages
- 1 broken link
Should I create a refactoring plan to fix these?
You: Yes
Agent: Here's the refactoring plan:
1. Merge UserAPI.md and user-api-reference.md -> api/users.md
2. Update 5 outdated sections to match current code
3. Link orphaned pages from main README or archive them
4. Fix broken link in README.md
Approve this plan?
You: Yes
Agent: Executing refactoring...
Done: Merged duplicate files
Done: Updated outdated sections
Done: Fixed orphaned pages
Done: Fixed broken links
Verification: All original content preserved, structure improved
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 · 200 lines · 112 tokens per session scan A 7f7ac369e5b3
docs-maintain is a command published in the GitHub repository acaprino/daodan (8 stars, last pushed 7d ago), licensed MIT. It adds 112 tokens to every session and 2,588 once invoked, about $0.0006 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 commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
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.