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.
git clone --depth 1 https://github.com/armanzeroeight/fastagent-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/armanzeroeight/fastagent-plugins/generate-docs)<a href="https://agentmods.dev/commands/armanzeroeight/fastagent-plugins/generate-docs"><img src="https://agentmods.dev/badge/commands/armanzeroeight/fastagent-plugins/generate-docs/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/armanzeroeight/fastagent-plugins/generate-docs"><img src="https://agentmods.dev/badge/commands/armanzeroeight/fastagent-plugins/generate-docs.svg" alt="Reviewed on agentmods" width="80" 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.00014 | $0.00651 |
| Opus 5.5 | $0.00006 | $0.00260 |
| Sonnet 5.5 | $0.00003 | $0.00130 |
| Haiku 4.5 | $0.00001 | $0.00065 |
Grade A, and why
generate-docs 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 1mo 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 — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Generate Documentation
Context
- Project type: !
ls package.json 2>/dev/null && echo "node" || (ls setup.py pyproject.toml 2>/dev/null && echo "python" || (ls go.mod 2>/dev/null && echo "go" || echo "unknown")) - Existing docs: !
ls README.md CHANGELOG.md docs/ 2>/dev/null - Git status: !
git log --oneline -5 2>/dev/null
Your Task
Generate or update project documentation based on the specified type.
Arguments
$1: Documentation type (optional, default: "all")readme- Generate/update README.mdapi- Generate API documentationchangelog- Update CHANGELOG.mdall- Generate all documentation
Steps
-
Detect project type and structure
-
Based on documentation type ($1):
For README:
- Analyze project structure and dependencies
- Identify key features from source code
- Select appropriate template (library, CLI, webapp, API)
- Generate comprehensive README with:
- Project description
- Installation instructions
- Usage examples
- API reference (if library)
- Contributing guidelines
For API docs:
- Scan for API routes/endpoints
- Extract JSDoc comments or docstrings
- Generate OpenAPI spec (for REST APIs)
- Create interactive documentation
For Changelog:
- Review git commits since last release
- Categorize changes (Added, Changed, Fixed, etc.)
- Format as Keep a Changelog entry
- Update CHANGELOG.md with new version
-
Validate generated documentation
-
Report what was created/updated
Output Format
# Documentation Generated
## README.md
✓ Created/Updated
- Project description added
- Installation instructions included
- Usage examples provided
- 5 sections total
## API Documentation
✓ Generated
- 12 endpoints documented
- OpenAPI spec created at docs/openapi.json
- Interactive docs available
## CHANGELOG.md
✓ Updated
- Version 2.1.0 entry added
- 3 new features
- 2 bug fixes
- 1 breaking change
Examples
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.
- 1mo ago First seen · 103 lines · 14 tokens per session scan A 2e73d925f6b9
generate-docs is a command published in the GitHub repository armanzeroeight/fastagent-plugins (29 stars, last pushed 2mo ago), licensed MIT. It adds 14 tokens to every session and 651 once invoked, about $0.0001 per session on Opus 5.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
aidd-churn
Rank files by hotspot score to identify prime candidates for refactoring before PR review.
trace-regression
Investigate a newly introduced bug or regression to identify the offending change and formulate a fix.
ml-run-review
Review a machine learning training run or experiment configuration for soundness, reproducibility, and evaluation rigor.
speckit.superspec.brainstorm
../../.opencode/commands/speckit.superspec.brainstorm.md.
kotlin-test
Enforce TDD workflow for Kotlin. Write Kotest tests first, then implement. Verify 80%+ coverage with Kover.
multi-workflow
Run a full multi-model development workflow with research, planning, execution, optimization, and review.