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 skills/littlebearapps/pitchdocs/user-guidesnpx skills add littlebearapps/pitchdocs --skill user-guidesgit 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/user-guides)<a href="https://agentmods.dev/skills/littlebearapps/pitchdocs/user-guides"><img src="https://agentmods.dev/badge/skills/littlebearapps/pitchdocs/user-guides.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.00065 | $0.01833 |
| Opus 5 | $0.00032 | $0.00916 |
| Sonnet 5 | $0.00013 | $0.00367 |
| Haiku 4.5 | $0.00006 | $0.00183 |
Grade A, and why
user-guides 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 5d 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 — 202 lines — stays where its author put it; the contents beside it link to each section on GitHub.
User Guide Generator
Philosophy
User guides answer the question: "How do I do [specific thing]?"
They complement the README (which sells and introduces) by providing detailed, task-oriented instructions for users who are already onboard.
Diataxis Framework
All documentation should be classified into one of four quadrants from the Diataxis framework. Each quadrant serves a different reader need:
| Quadrant | Purpose | Reader State | Directory |
|---|---|---|---|
| Tutorials | Learning-oriented lessons | "I want to learn" | docs/tutorials/ |
| How-to Guides | Task-oriented recipes | "I want to do X" | docs/guides/ |
| Reference | Information-oriented lookup | "I need to check Y" | docs/reference/ or docs/api/ |
| Explanation | Understanding-oriented context | "I want to understand why" | docs/explanation/ |
Rules:
- Classify every document into exactly one quadrant before writing — don't mix tutorial prose with reference tables
- Tutorials walk through a complete learning journey; guides solve a specific task
- Reference docs are dry, accurate, and complete. Explanation docs cover architecture decisions and "why".
- At minimum, provide How-to Guides (this skill's primary output) and link to any existing reference docs
- During guide discovery (Step 1), classify each existing doc into a quadrant. Flag any quadrant with zero documents.
See SKILL-reference.md for frontmatter field tables and title conventions.
Guide Structure
Directory Layout
docs/
├── tutorials/ # Learning-oriented lessons (Diataxis: Tutorial)
│ └── build-your-first-app.md
├── guides/ # Task-oriented how-to recipes (Diataxis: How-to)
│ ├── getting-started.md # First-time setup, expanded quickstart
│ ├── configuration.md # All config options explained
│ ├── [task-name].md # One guide per common task
│ └── troubleshooting.md # Common problems and solutions
├── reference/ # Information-oriented lookup (Diataxis: Reference)
│ ├── api.md # API reference
│ └── cli.md # CLI reference
├── explanation/ # Understanding-oriented context (Diataxis: Explanation)
│ └── architecture.md # Design decisions and architecture
└── README.md # Docs index / hub page
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.
- 5d ago First seen · 202 lines · 65 tokens per session scan A 45caaa75ca80
user-guides is a skill published in the GitHub repository littlebearapps/pitchdocs (8 stars, last pushed 4mo ago), licensed MIT. It adds 65 tokens to every session and 1,833 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
golden-jupyter-dir
Use when testing the goldenjupyterdir golden build.
golden-epub
Use when testing the epub golden build.
golden-man-kw
Use when testing the man golden build.
skill-builder
Automatically detect source types and build AI skills using Skill Seekers. Use when the user wants to create skills from documentation, repos, PDFs, videos, or other knowledge sources.
golden-chat-topics
Use when testing the goldenchattopics golden build.
golden-chat-single
Use when testing the goldenchatsingle golden build.