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/pmndrs/claude-code-plugin/docsnpx skills add pmndrs/claude-code-plugin --skill docsgit clone --depth 1 https://github.com/pmndrs/claude-code-pluginWhat 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.00063 | $0.00521 |
| Opus 5 | $0.00032 | $0.00260 |
| Sonnet 5 | $0.00013 | $0.00104 |
| Haiku 4.5 | $0.00006 | $0.00052 |
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 yesterday.
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
pmndrs docs
The pmndrs MCP server serves the official docs from docs.pmnd.rs. Prefer it over
memory: these libraries move fast and recalled APIs go stale.
The same server also serves the example gallery — see pmndrs:examples. The docs say
what an API takes; an example shows a whole scene that works. A question about how
something is put together usually wants both, in that order: find the demo, then
confirm against the docs that its API is still current.
Always index first
Never guess a page path — get_page_content matches exactly, and route shapes differ
per library (/api/hooks for react-three-fiber, /learn/guides/... and
/reference/apis/... for zustand, /abstractions/... for drei). Read the index
resource, pick the path, then fetch.
ReadMcpResourceToolondocs://{lib}/index— one{path} - {title}per line, 200–1,300 tokens.mcp__pmndrs__get_page_contentwithliband the exactpathfrom step 1.
A bad path returns MCP server error: Page not found: {path} — re-read the index
instead of retrying variants.
Coverage
Served — route these through the MCP: react-three-fiber, drei, zustand, docs
(the generator itself). Names are case-sensitive.
Anything else is unserved. The tool's lib enum advertises more libraries than that,
but the extra entries have no llms-full.txt behind them: every call fails and every
index comes back empty. Treat a library missing from the list above as absent, and use
WebFetch on its docs site. Fix in flight: pmndrs/docs#555.
Budget
Pages run 1,200–4,000 tokens each. Fetch the one page that answers the question. If three or more look relevant, read the index titles first and narrow — don't fetch the set and sort it out afterwards.
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.
- yesterday First seen · 45 lines · 63 tokens per session scan A 40fe19734276
docs is a skill published in the GitHub repository pmndrs/claude-code-plugin (5 stars, last pushed 18d ago), licensed MIT. It adds 63 tokens to every session and 521 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…