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/activategit 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.00018 | $0.01393 |
| Opus 5 | $0.00009 | $0.00696 |
| Sonnet 5 | $0.00004 | $0.00279 |
| Haiku 4.5 | $0.00002 | $0.00139 |
Grade A, and why
activate 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 — 137 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/activate
Install PitchDocs' advisory rules and docs-freshness agent into the current project. By default, PitchDocs only provides commands globally — the rules that suggest documentation improvements and the agent that checks freshness are opt-in per-project.
PitchDocs has two tiers:
- Standard (default): Advisory. Doc-standards and docs-awareness rules auto-load for this project. The docs-freshness agent is available for quick freshness checks.
- Strict (opt-in): Adds the content-filter-guard hook, which blocks writing high-risk OSS files (CODE_OF_CONDUCT.md, LICENSE, SECURITY.md) and advises on medium-risk files. Claude Code only.
Behaviour
- Determine the plugin's install location (the directory containing this command file)
- Execute the requested action:
install,install strict,uninstall, orstatus
Arguments
-
install: Install PitchDocs Standard into the current project:- Create
.claude/rules/directory if it does not exist - Copy
doc-standards.mdanddocs-awareness.mdfrom the plugin'srules/directory to.claude/rules/ - Create
.claude/agents/directory if it does not exist - Copy
docs-freshness.mdfrom the plugin'sagents/directory to.claude/agents/ - Report what was installed
- Create
-
install strict: Install PitchDocs Standard + Strict into the current project:- Perform all steps from
installabove - Create
.claude/hooks/directory if it does not exist - Copy
content-filter-guard.shfrom the plugin'shooks/directory to.claude/hooks/ - Make the script executable (
chmod +x) - Merge a PreToolUse Write hook entry into
.claude/settings.json(create the file if needed; if the entry already exists, do not duplicate it) - Report what was installed, noting Strict tier is active
- Perform all steps from
-
uninstall: Remove all PitchDocs per-project features:- Remove
.claude/rules/doc-standards.mdand.claude/rules/docs-awareness.md - Remove
.claude/agents/docs-freshness.md - Remove
.claude/hooks/content-filter-guard.shif present - Remove the content-filter-guard PreToolUse Write hook entry from
.claude/settings.jsonif present (preserve other hooks) - Report what was removed
- Remove
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 · 137 lines · 18 tokens per session scan A 1bbd9db329f2
activate is a command published in the GitHub repository littlebearapps/pitchdocs (7 stars, last pushed 3mo ago), licensed MIT. It adds 18 tokens to every session and 1,393 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.