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/littlebearapps/pitchdocs/user-guidegit clone --depth 1 https://github.com/littlebearapps/pitchdocsWhat 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.00012 | $0.00535 |
| Opus 5 | $0.00006 | $0.00267 |
| Sonnet 5 | $0.00002 | $0.00107 |
| Haiku 4.5 | $0.00001 | $0.00053 |
Grade A, and why
user-guide 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.
What it actually says
/user-guide
Generate task-oriented user guides and how-to documentation.
Behaviour
- Load the
user-guidesskill for structure and templates - Load the
doc-standardsrule for tone and language - If GitHub MCP tools are unavailable (GitLab/Bitbucket), gather equivalent data via
glabCLI, REST API, or git history - Analyse the project to determine what guides are needed:
- Check existing docs for gaps
- Scan GitHub issues/discussions for common questions
- Identify config files, CLI commands, and workflows users need to understand
- Generate guide files in
docs/guides/ - Create or update
docs/README.mdas a hub page - Update
README.mdto link to the documentation section
Arguments
- No arguments: analyses project and generates the most-needed guides
- Topic name (e.g.,
deployment,configuration): generates a specific guide all: generates the full guide suite (getting-started, configuration, deployment, troubleshooting)hub: only generates the docs/README.md hub page linking existing guides
Guide Priority
- Getting Started — always generated first (expanded quickstart)
- Configuration — if config files or env vars exist
- Task-specific guides — based on project features and common questions
- Deployment — if the project has deploy scripts or CI/CD
- Migration — if there are breaking version changes
- Troubleshooting — compiled from closed issues and error patterns
Output
- Creates
docs/guides/directory structure - Creates
docs/README.mdhub page - Updates
README.mdwith documentation links section - Each guide follows the numbered-steps format with verification steps
Cross-Linking
After generating guides, ensure:
- README.md links to
docs/README.mdand key guides - CONTRIBUTING.md links to getting-started guide
- Each guide links to related guides and back to the hub
- Troubleshooting guide is referenced from other guides' error sections
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 · 62 lines · 12 tokens per session scan A 24c5cca6bb26
user-guide is a command published in the GitHub repository littlebearapps/pitchdocs (7 stars, last pushed 3mo ago), licensed MIT. It adds 12 tokens to every session and 535 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
create-skill
Create an AI skill from any source (URL, repo, PDF, video, notebook, etc.).
install-skill
One-command skill creation and packaging for a target platform.
sync-config
Sync a scraping config's URLs against the live documentation site.
review-renovate
Review and merge renovate PRs with automerge configuration updates.
monitor-ci
Monitors pull request CI checks until they are resolved (pass or fail).
/add-claude-rule
Appends the rule from $ARGUMENTS to CLAUDE.md.