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 rsts-dev/claude-buddy-marketplace --skill docsgit clone --depth 1 https://github.com/rsts-dev/claude-buddy-marketplaceWrote 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/rsts-dev/claude-buddy-marketplace/docs)<a href="https://agentmods.dev/skills/rsts-dev/claude-buddy-marketplace/docs"><img src="https://agentmods.dev/badge/skills/rsts-dev/claude-buddy-marketplace/docs.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.00044 | $0.00353 |
| Opus 5 | $0.00022 | $0.00177 |
| Sonnet 5 | $0.00009 | $0.00071 |
| Haiku 4.5 | $0.00004 | $0.00035 |
Grade A, and why
Docs 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.
What it actually says
Docs
Generate comprehensive technical documentation by analyzing the codebase with foundation-specific templates.
Customization
Before executing, check for user customizations at:
~/.claude/LIFEOS/USER/CUSTOMIZATIONS/SKILLS/Docs/
If this directory exists, load and apply any PREFERENCES.md configurations. If not, proceed with defaults.
Prerequisites
- LifeOS must be installed. Check
~/.claude/LIFEOS/VERSION. - Foundation must exist at
/directive/foundation.md.
Workflow Routing
| Workflow | Trigger | File |
|---|---|---|
| GenerateDocs | Any invocation | Workflows/GenerateDocs.md |
Template Selection
Based on foundation type:
- Default:
Templates/DefaultDocs.md - JHipster:
Templates/JHipsterDocs.md - MuleSoft:
Templates/MuleSoftDocs.md
Output
Documentation is generated in the docs/ directory with a navigation index at docs/README.md.
Examples
Example 1: Generate documentation
User: "/buddy:docs"
-> Verifies foundation exists, extracts type
-> Analyzes codebase (structure, APIs, models, configs)
-> Loads DefaultDocs.md template
-> Generates: architecture.md, api-reference.md, setup.md, deployment.md
-> Creates docs/README.md as navigation index
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 · 50 lines · 44 tokens per session scan A e1e27308a44e
Docs is a skill published in the GitHub repository rsts-dev/claude-buddy-marketplace (17 stars, last pushed 16d ago), licensed MIT. It adds 44 tokens to every session and 353 once invoked, about $0.0002 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…