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 skills add littlebearapps/pitchdocs --skill pitchdocs-suitegit 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/skills/littlebearapps/pitchdocs/pitchdocs-suite)<a href="https://agentmods.dev/skills/littlebearapps/pitchdocs/pitchdocs-suite"><img src="https://agentmods.dev/badge/skills/littlebearapps/pitchdocs/pitchdocs-suite.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.1 | $0.00058 | $0.01879 |
| Opus 5 | $0.00029 | $0.00940 |
| Sonnet 5 | $0.00012 | $0.00376 |
| Haiku 4.5 | $0.00006 | $0.00188 |
Grade A, and why
pitchdocs-suite 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 7d 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 — 146 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repository Documentation Suite
Complete Docs Inventory
A well-documented public repository should have these files:
Platform note: The file paths below use GitHub conventions. For GitLab or Bitbucket repositories, load the platform-profiles skill for equivalent paths (e.g. .gitlab/issue_templates/ instead of .github/ISSUE_TEMPLATE/).
Tier 1: Essential (Every Public Repo)
| File | Purpose | Generator |
|---|---|---|
README.md |
First impression, value proposition, quickstart | public-readme skill |
LICENSE |
Legal terms for usage — see LICENSE Selection Framework below | Auto-detect from package.json |
CONTRIBUTING.md |
How to contribute code, report bugs, suggest features | This skill |
.github/ISSUE_TEMPLATE/bug_report.yml |
Structured bug reports | This skill |
.github/ISSUE_TEMPLATE/feature_request.yml |
Feature proposals | This skill |
.github/PULL_REQUEST_TEMPLATE.md |
PR checklist and description template | This skill |
Tier 2: Professional (Active Projects)
| File | Purpose | Generator |
|---|---|---|
CHANGELOG.md |
User-facing change history | changelog skill |
SUPPORT.md |
Where to get help — issues, discussions, external channels | This skill |
.github/release.yml |
Auto-generated release note categories | This skill |
llms.txt |
LLM-friendly content index for AI tools (Cursor, Windsurf, Claude Code) | llms-txt skill |
AGENTS.md |
Cross-tool AI agent context — conventions, architecture, key commands | ContextDocs plugin (install separately) |
.github/copilot-instructions.md |
GitHub Copilot repository-level instructions | ContextDocs plugin (install separately) |
.windsurfrules |
Windsurf (Cascade AI) project-level context | ContextDocs plugin (install separately) |
.clinerules |
Cline VS Code extension project-level context | ContextDocs plugin (install separately) |
CODE_OF_CONDUCT.md |
Community behaviour standards | This skill |
SECURITY.md |
Vulnerability reporting process | This skill |
.github/ISSUE_TEMPLATE/config.yml |
Issue template chooser config | This skill |
.github/FUNDING.yml |
Sponsorship links (GitHub only) | This skill |
docs/README.md |
Documentation hub page | user-guides skill |
docs/guides/getting-started.md |
Expanded quickstart for new users | user-guides skill |
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 7d ago First seen · 146 lines · 58 tokens per session scan A e3c73de491d6
pitchdocs-suite is a skill published in the GitHub repository littlebearapps/pitchdocs (8 stars, last pushed 4mo ago), licensed MIT. It adds 58 tokens to every session and 1,879 once invoked, about $0.0003 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 skills, from other repositories
docs
Generate and update living documentation — tech docs, user guides, philosophy overview. Composable building block for CLOSE and other skills.
init-rpm
Project setup and verification. First run creates rpm context for a project. Repeat runs verify that an existing rpm setup matches the latest expected layout and apply safe migrations.
root-cause-first
A debugging discipline that requires finding the underlying cause of a bug before changing the code. It also sets rules for handling errors, fallbacks, retries, and temporary diagnostics.
backlog
Manage the rpm backlog (long-term project tasks in docs/rpm/future/tasks.org — distinct from Claude's native TaskCreate list, which is session-scoped). Add, list, review, postpone, or complete entries. TRIGGER on natural-language backlog operations — phrasings like "backlog X", "add X to backlog", "add to backlog"…
growing-docs
Use when a repo already has baseline docs but a demand signal says they are no longer enough — the same question answered twice, a fact re-derived the hard way across sessions, an incident with no runbook, onboarding pain, a recurring "why is it like this?", someone asking "should we document X?", or a…
refresh
Use when an existing contextualizer's references may have drifted from current upstream state — typically weekly, or whenever a few days of upstream changes have accumulated — to bring them back into agreement.