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 public-readmegit 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/public-readme)<a href="https://agentmods.dev/skills/littlebearapps/pitchdocs/public-readme"><img src="https://agentmods.dev/badge/skills/littlebearapps/pitchdocs/public-readme.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.01749 |
| Opus 5 | $0.00029 | $0.00874 |
| Sonnet 5 | $0.00012 | $0.00350 |
| Haiku 4.5 | $0.00006 | $0.00175 |
Grade A, and why
public-readme 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 8d 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 — 167 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Public README Generator
README Structure (Recommended Order)
Output formatting conventions (see doc-standards rule for the full reference):
- Prefix each H2 section heading with an emoji from the standard table
- Separate major sections with
---horizontal rules - The numbered sections below (1–9) indicate recommended ORDER — the actual output uses H2 headings with emoji prefixes, not numbered H3s
GEO: Optimising for AI Citation
Load the geo-optimisation skill for the full GEO reference. README-specific essentials:
- First paragraph as standalone definition — The bold one-liner must work if extracted with no surrounding context
- Comparison section — Include "How It Compares" with a feature table (LLMs surface these for "X vs Y" queries)
- Statistics and benchmarks — Embed concrete numbers in feature descriptions (28% more AI visibility)
- Semantic heading hierarchy — Strict H1 > H2 > H3, descriptive topic-keyword headings
- Atomic feature descriptions — Each bullet/row comprehensible without surrounding context
1. Hero Section
Full hero template:
<p align="center">
<img src="docs/assets/logo.svg" height="200" alt="Project Name" />
</p>
<p align="center">
<strong>One compelling sentence that explains the value proposition — not what it IS, but what it DOES FOR YOU.</strong>
</p>
<p align="center">
<a href="link"><img src="https://img.shields.io/github/actions/workflow/status/org/repo/ci.yml?branch=main" alt="Build" /></a>
<a href="link"><img src="https://img.shields.io/codecov/c/github/org/repo" alt="Coverage" /></a>
<a href="link"><img src="https://img.shields.io/npm/v/package-name" alt="npm" /></a>
<a href="link"><img src="https://img.shields.io/github/license/org/repo" alt="License" /></a>
<a href="link"><img src="https://img.shields.io/npm/dm/package-name" alt="Downloads" /></a>
</p>
<p align="center">
<a href="link">Documentation</a> · <a href="link">Examples</a> · <a href="link">Discord</a> · <a href="link">Blog</a>
</p>
---
What ships with it
1 file 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.
- 8d ago First seen · 167 lines · 58 tokens per session scan A dc639948d433
public-readme 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,749 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.
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.
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"…
using-skill-engine
When the user mentions skill-engine or "the engine" without naming a specific workflow, or wants first-run setup. Inspects .claude/skills/-context/ install state (and any pending -context.proposed/ proposals) across all three install levels, then dispatches to engine-bootstrap when no contextualizer exists, to…