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/krmcbride/claude-plugins/documentation-lookupnpx skills add krmcbride/claude-plugins --skill documentation-lookupgit clone --depth 1 https://github.com/krmcbride/claude-pluginsWrote 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/krmcbride/claude-plugins/documentation-lookup)<a href="https://agentmods.dev/skills/krmcbride/claude-plugins/documentation-lookup"><img src="https://agentmods.dev/badge/skills/krmcbride/claude-plugins/documentation-lookup.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.00034 | $0.00380 |
| Opus 5 | $0.00017 | $0.00190 |
| Sonnet 5 | $0.00007 | $0.00076 |
| Haiku 4.5 | $0.00003 | $0.00038 |
Grade A, and why
documentation-lookup scanned grade A with 1 finding 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 4d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -s "https://context7.com/api/v2/search?query={library_name}" | jq '.results[:3]' What it actually says
Documentation Lookup
When to activate:
- User says "check the docs"
- User needs API documentation or code examples
- User mentions a library/framework name
- Source code of a library is not available locally
Two-step process:
Step 1: Find the library ID
Search for the library to get its context7 ID:
curl -s "https://context7.com/api/v2/search?query={library_name}" | jq '.results[:3]'
Example - searching for "react":
curl -s "https://context7.com/api/v2/search?query=react" | jq '.results[:3] | .[] | {id, title}'
This returns matching libraries. Use the id field (e.g., /facebook/react or /websites/react_dev).
Step 2: Fetch documentation
Use the library ID from step 1:
curl -s "https://context7.com/api/v2/docs/code{library_id}?topic={topic}&page=1"
Example - fetching React hooks docs:
curl -s "https://context7.com/api/v2/docs/code/facebook/react?topic=hooks&page=1"
Parameters:
topic- Focus area (e.g.,hooks,routing,authentication)page- Pagination (1-10), use if first page doesn't have enough info
Response: Returns markdown-formatted documentation snippets with code examples.
Fallback: If context7 doesn't have the library or returns errors, use web search.
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.
- 4d ago First seen · 55 lines · 34 tokens per session scan A f6b17607fea3
documentation-lookup is a skill published in the GitHub repository krmcbride/claude-plugins (3 stars, last pushed 8mo ago), licensed MIT. It adds 34 tokens to every session and 380 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). 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.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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…