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/tommymorgan/claude-plugins/generate-docsgit clone --depth 1 https://github.com/tommymorgan/claude-pluginsWhat 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.00019 | $0.00574 |
| Opus 5 | $0.00010 | $0.00287 |
| Sonnet 5 | $0.00004 | $0.00115 |
| Haiku 4.5 | $0.00002 | $0.00057 |
Grade A, and why
tommymorgan: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 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.
How it starts
The opening of the file, as written. The whole thing — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Generate Documentation from Living Specifications
Generate user documentation, developer documentation, or both from living .feature files.
Usage
/tommymorgan:generate-docs user
/tommymorgan:generate-docs dev
/tommymorgan:generate-docs both [project-path]
What This Does
User Documentation (@user scenarios only):
- Filters scenarios tagged @user
- Converts Gherkin to readable prose
- Excludes all technical implementation details
- Creates user-friendly guide
Developer Documentation (@technical scenarios):
- Filters scenarios tagged @technical
- Includes implementation requirements
- Shows expected system behavior
- Documents technical specifications
Evolutionary Updates:
- Preserves existing introduction and non-scenario content
- Updates only changed scenarios
- Maintains documentation voice and style
- Keeps custom examples and diagrams
Process
cd $PROJECT_PATH
# Generate user docs
python3 tools/claude-plugins/tommymorgan/migration/commands/doc_generator.py generate features/ docs/user-guide.md --tags @user
# Generate developer docs
python3 tools/claude-plugins/tommymorgan/migration/commands/doc_generator.py generate features/ docs/technical-spec.md --tags @technical
Output
User Documentation (docs/user-guide.md):
# User Guide
## Introduction
(Preserved from existing docs)
## Authentication
### Logging In
User logs in successfully: i am on the login page, i enter valid credentials, i am redirected to dashboard.
### Resetting Password
User resets forgotten password: i click forgot password, i enter my email, i receive reset link.
Developer Documentation (docs/technical-spec.md):
# Technical Specification
## Authentication API
### JWT Token Generation
JWT token generation: user authenticates successfully, auth service processes request, jwt token is issued with user claims, token expires in 24 hours.
Benefits
- Always accurate: Generated from living specs (source of truth)
- No duplication: One source for both user and dev docs
- Test-aligned: Docs match what tests verify
- Evolutionary: Preserves manual content while updating scenarios
- Accessible: Generates semantic HTML when needed
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 · 98 lines · 19 tokens per session scan A a0d93252db54
tommymorgan:generate-docs is a command published in the GitHub repository tommymorgan/claude-plugins (4 stars, last pushed 1mo ago), licensed MIT. It adds 19 tokens to every session and 574 once invoked, about $0.0001 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
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.
constitution
Create or update the project constitution from interactive or provided principle inputs.
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.