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 instructions/littlebearapps/pitchdocs/claude-mdgit clone --depth 1 https://github.com/littlebearapps/pitchdocsWrote 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/instructions/littlebearapps/pitchdocs/claude-md)<a href="https://agentmods.dev/instructions/littlebearapps/pitchdocs/claude-md"><img src="https://agentmods.dev/badge/instructions/littlebearapps/pitchdocs/claude-md.svg" alt="Measured on agentmods" 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 | $0.02035 | $0.02035 |
| Opus 5 | $0.01018 | $0.01018 |
| Sonnet 5 | $0.00407 | $0.00407 |
| Haiku 4.5 | $0.00203 | $0.00203 |
Grade A, and why
pitchdocs CLAUDE.md 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 4d 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 — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PitchDocs
Generate high-quality public-facing repository documentation with a marketing edge. PitchDocs is a Claude Code plugin (pure Markdown, zero runtime dependencies) with 15 skills, 4 agents (3 pipeline + 1 per-project), 3 auto-loaded rules (1 global + 2 installed), 2 installable rule templates, 16 slash commands (14 active + 2 stubs), 1 opt-in hook, and 24 eval test cases. This repo also has ContextDocs installed, which adds the context-updater agent and context-quality.md rule.
Project Architecture
This is a 100% Markdown-based plugin — no JavaScript, no Python, no build step. All knowledge lives in structured YAML+Markdown files:
.claude-plugin/plugin.json → Plugin manifest (name, version, keywords)
.claude/skills/*/SKILL.md → 16 reference knowledge modules (loaded on-demand)
.claude/agents/docs-writer.md → Orchestration agent (coordinates researcher → write → reviewer pipeline)
.claude/agents/docs-researcher.md → Codebase discovery and feature extraction agent
.claude/agents/docs-reviewer.md → Post-generation quality validation agent
.claude/agents/context-updater.md → AI context file updater agent (from ContextDocs, not PitchDocs)
.claude/agents/docs-freshness.md → Installed freshness checker (auto-loaded locally; source: agents/docs-freshness.md)
.claude/rules/content-filter.md → Content filter quick reference (auto-loaded; Claude Code only)
.claude/rules/context-quality.md → AI context file quality standards (from ContextDocs, auto-loaded; Claude Code only)
.claude/rules/doc-standards.md → Installed quality standards (auto-loaded locally; source: rules/doc-standards.md)
.claude/rules/docs-awareness.md → Installed documentation trigger map (auto-loaded locally; source: rules/docs-awareness.md)
rules/doc-standards.md → Quality standards (installed per-project by /pitchdocs:activate)
rules/docs-awareness.md → Documentation trigger map (installed per-project by /pitchdocs:activate)
agents/docs-freshness.md → Freshness checker agent (installed per-project by /pitchdocs:activate)
commands/*.md → 16 slash command definitions (14 active + 2 stubs redirecting to ContextDocs)
hooks/*.sh → 1 opt-in hook script (Claude Code only, installed by /pitchdocs:activate install strict)
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.
- 4d ago First seen · 97 lines · 2,035 tokens per session scan A 69475aa80374
pitchdocs CLAUDE.md is an instructions file published in the GitHub repository littlebearapps/pitchdocs (8 stars, last pushed 3mo ago), licensed MIT. It adds 2,035 tokens to every session, about $0.0102 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 instructions, from other repositories
Skill_Seekers CLAUDE.md
Instructions for yusufkaraaslan/Skill_Seekers, covering claude.md, project overview, essential commands, required before running tests or cli (src/ layout) and run all tests (never skip - all must pass before commits).
Skill_Seekers AGENTS.md
Instructions for yusufkaraaslan/Skill_Seekers, covering agents.md - skill seekers, project overview, key capabilities, setup and with dev tools (pytest, ruff, mypy, coverage).
docs.page AGENTS.md
AGENTS.md instructions for invertase/docs.page, covering docs.page — agent guidance, project overview, monorepo layout, commands and conventions.
han CLAUDE.md
Claude Code instructions for testdouble/han, covering han: project map, creating skills, agents, or other plugin aspects, repository layout, when to use which doc and entry points.
ottonomous CLAUDE.md
Instructions for brsbl/ottonomous, covering ottonomous repository guide, product contract, skill behavior, spec and review.
docflow AGENTS.md
Instructions for MedAdemBHA/docflow, a project described as: Documentation memory for AI coding agents—route project knowledge, reduce repeated context loading, and validate living Markdown docs.