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/buildmoonshot/skillpacks/check-the-docsnpx skills add buildmoonshot/skillpacks --skill check-the-docsgit clone --depth 1 https://github.com/buildmoonshot/skillpacksWrote 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/buildmoonshot/skillpacks/check-the-docs)<a href="https://agentmods.dev/skills/buildmoonshot/skillpacks/check-the-docs"><img src="https://agentmods.dev/badge/skills/buildmoonshot/skillpacks/check-the-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 | $0.00071 | $0.00424 |
| Opus 5 | $0.00036 | $0.00212 |
| Sonnet 5 | $0.00014 | $0.00085 |
| Haiku 4.5 | $0.00007 | $0.00042 |
Grade A, and why
check-the-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 3d 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
Check the Docs
Before calling into an external library or API, confirm the API is real and current — do not code it from memory and hope.
When to stop and check
- You're reaching for a method, option, or parameter and you're not certain it exists with that exact name/shape.
- The library has had major version changes (the API you remember may be gone).
- It's niche or fast-moving — small libraries and recent releases are where memory is least reliable.
- The user reported an error that looks like a wrong signature (
X is not a function, unexpected argument).
What to do
- Verify the signature against current documentation, the installed version's types/source, or an official reference — not your recollection.
- Check the installed version. Read
package.json/ lockfile /requirements.txt. Match the docs to that version, not the latest. - Prefer the project's existing usage. If the codebase already calls this library, copy that real, working pattern over anything you'd reconstruct from memory.
When you can't verify
Say so, and mark the call as unverified: "I used client.search(...) from memory — confirm this matches your installed version, as I couldn't check the docs." An honest flag beats a confident hallucination.
Why this matters
Hallucinated API calls are the classic agent failure: confident, plausible, and completely wrong — array.removeWhere(), a timeout option that doesn't exist, a renamed method from three versions ago. They cost a debugging session to track down. Thirty seconds of checking prevents them.
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.
- 3d ago First seen · 30 lines · 71 tokens per session scan A c44e4e2dec99
check-the-docs is a skill published in the GitHub repository buildmoonshot/skillpacks (2 stars, last pushed 2mo ago), licensed MIT. It adds 71 tokens to every session and 424 once invoked, about $0.0004 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
bridge
Use when the user wants hyperflow's behavioral rules to apply outside the terminal CLI — in Claude Code Desktop, claude.ai web, or IDE extensions that don't load CLI plugins. Writes a managed doctrine block into the project's CLAUDE.md so autonomy + intent-routing + commit cadence + role separation + file-first rules…
fable-method
A step-by-step problem-solving loop (classify the ask, define done, gather evidence, decide, act surgically, verify by observation, report outcome-first). Use when the user says "/fable-method", "use the fable method", or "approach this like Fable", or proactively when starting any multi-step task that no…
fable-domain
Discuss a domain with the user, research it from real sources, then generate a trusted skill bundle for it - a step-by-step workflow with a flowchart, a domain adapter, a trap fixture, and a smoke eval. Use when the user says "/fable-domain ", "make a skill for ", "add a domain to the fable method", or "give a lesser…
writers-pattern
Add a new platform writer module in src/writers/ that generates and writes agent config files for a supported platform. Each writer exports a function that accepts a config interface, creates directories (rules/, skills/, mcp configs), writes files with proper formatting and frontmatter, and returns string[] of…
caliber-testing
Writes Vitest tests following project patterns: tests/ directories, vi.mock() for module mocking with vi.hoisted() for test-time factories, global LLM mock from src/test/setup.ts, environment variable save/restore in beforeEach/afterEach, vi.clearAllMocks() lifecycle, and test file organization. Use when user says…
llm-provider
Adds a new LLM provider implementing LLMProvider interface with call() and stream() methods. Integrates with provider factory in src/llm/index.ts, config detection in src/llm/config.ts, and error handling via tracking and recovery. Use when adding a new model backend, integrating a third-party LLM API, or extending…