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/composio-community/awesome-claude-plugins/documentation-generatorgit clone --depth 1 https://github.com/composio-community/awesome-claude-pluginsWrote 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/composio-community/awesome-claude-plugins/documentation-generator)<a href="https://agentmods.dev/commands/composio-community/awesome-claude-plugins/documentation-generator"><img src="https://agentmods.dev/badge/commands/composio-community/awesome-claude-plugins/documentation-generator.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 | $0.00007 | $0.00151 |
| Opus 5 | $0.00003 | $0.00076 |
| Sonnet 5 | $0.00001 | $0.00030 |
| Haiku 4.5 | $0.00001 | $0.00015 |
Grade A, and why
documentation-generator 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 4d 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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.
- 4d ago First seen · 29 lines · 7 tokens per session scan A 96d3acb009d0
documentation-generator is a command published in the GitHub repository composio-community/awesome-claude-plugins (1,924 stars, last pushed 1mo ago), with no licence file. It adds 7 tokens to every session and 151 once invoked, about $0.0000 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 commands, from other repositories
create
Create a custom auto-develop loop for any feature in your codebase.
evolve-rubric
Evolve an auto-improve rubric by analyzing results and finding quality gaps.
evolve-spec
Evolve an auto-develop capability spec by analyzing results and discovering new capabilities.
feature-new
Design and implement a new feature with parallel best-practice research, codebase exploration, architectural planning, atomic phase specs, phase-by-phase code review, and automated documentation.
feature-refactor
Refactor an existing feature with deep code understanding, documentation review, atomic phase breakdown, incremental changes, and comprehensive review loops.
feature:bugfix
Systematic bug investigation and fixing workflow for existing features. Uses code-reviewer for deep analysis, code-consolidator for context, parallel web research for solutions, and atomic phase implementation with review gates.