activate

A project command for installing, removing, or checking PitchDocs documentation rules and its documentation-freshness checker. It can also enable stricter checks for certain open-source files in Claude Code.

In plain words
What is it for?
Use it to set up PitchDocs in a project, choose Standard or Strict checks, remove the setup, or see its current status.
Why use it?
It lets a project choose which documentation guidance and checks are active instead of applying them everywhere. The strict option helps flag or block changes to sensitive files such as LICENSE and SECURITY.md.

Command

Install

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.

agentmods
npx agentmods add commands/littlebearapps/pitchdocs/activate
Clone the repo
git clone --depth 1 https://github.com/littlebearapps/pitchdocs
Per session 18 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,393 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce 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

Measured 2d ago against content hash 1bbd9db329f2, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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.

commands/activate.md · 137 lines

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

  1. Determine the plugin's install location (the directory containing this command file)
  2. Execute the requested action: install, install strict, uninstall, or status

Arguments

  • install: Install PitchDocs Standard into the current project:

    1. Create .claude/rules/ directory if it does not exist
    2. Copy doc-standards.md and docs-awareness.md from the plugin's rules/ directory to .claude/rules/
    3. Create .claude/agents/ directory if it does not exist
    4. Copy docs-freshness.md from the plugin's agents/ directory to .claude/agents/
    5. Report what was installed
  • install strict: Install PitchDocs Standard + Strict into the current project:

    1. Perform all steps from install above
    2. Create .claude/hooks/ directory if it does not exist
    3. Copy content-filter-guard.sh from the plugin's hooks/ directory to .claude/hooks/
    4. Make the script executable (chmod +x)
    5. Merge a PreToolUse Write hook entry into .claude/settings.json (create the file if needed; if the entry already exists, do not duplicate it)
    6. Report what was installed, noting Strict tier is active
  • uninstall: Remove all PitchDocs per-project features:

    1. Remove .claude/rules/doc-standards.md and .claude/rules/docs-awareness.md
    2. Remove .claude/agents/docs-freshness.md
    3. Remove .claude/hooks/content-filter-guard.sh if present
    4. Remove the content-filter-guard PreToolUse Write hook entry from .claude/settings.json if present (preserve other hooks)
    5. Report what was removed

Read the full file on GitHub · 137 lines

Changes

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.

  1. 2d ago First seen · 137 lines · 18 tokens per session scan A 1bbd9db329f2

Subscribe to this mod's changes

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.