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/arvindand/agent-skills/context7npx skills add arvindand/agent-skills --skill context7git clone --depth 1 https://github.com/arvindand/agent-skillsWrote 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/arvindand/agent-skills/context7)<a href="https://agentmods.dev/skills/arvindand/agent-skills/context7"><img src="https://agentmods.dev/badge/skills/arvindand/agent-skills/context7.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.00100 | $0.00844 |
| Opus 5 | $0.00050 | $0.00422 |
| Sonnet 5 | $0.00020 | $0.00169 |
| Haiku 4.5 | $0.00010 | $0.00084 |
Grade A, and why
context7 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.
How it starts
The opening of the file, as written. The whole thing — 78 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Context7 Documentation Lookup
Use ${CLAUDE_SKILL_DIR}/scripts/context7.py to fetch current library documentation without MCP tool-schema overhead.
This is an execution skill. Decide whether to search or fetch directly, run the script, then use the returned docs to answer. Keep the main flow lean and load REFERENCES.md only when you need example commands, common library IDs, or troubleshooting details.
When to Use
Activate when the user asks for:
- current library or framework APIs
- official code examples or implementation patterns
- version-specific docs or migration guidance
- third-party tool setup that depends on vendor docs
- documentation for libraries in npm, PyPI, or similar ecosystems
Core Workflow
-
If you already know the library ID, skip search and call:
python3 ${CLAUDE_SKILL_DIR}/scripts/context7.py docs <library-id> [topic] [mode] -
If the library ID is unclear, search first:
python3 ${CLAUDE_SKILL_DIR}/scripts/context7.py search "<query>" -
Pick the best matching library ID, then fetch docs.
-
Use the returned docs to answer with version-aware guidance and cite the source URL when the script provides one.
Decision Rules
- Search only when the library ID is unclear or ambiguous.
- Use
codemode (default) for API references, function signatures, and implementation examples. - Use
infomode for conceptual guides, architecture, and migration-heavy questions. - Use a focused topic first; broaden it if results are empty or off-target.
- For version-specific docs, append the full upstream tag to the library ID (for example
/vercel/next.js/v15.1.8), or include the version in the topic. A bare major such as/vercel/next.js/15does not resolve.
If syntax is unclear, run:
python3 ${CLAUDE_SKILL_DIR}/scripts/context7.py --help
Output Rules
- Prefer official patterns over generic recall when the docs provide a direct answer.
- Keep the answer tied to the user's requested library and version.
- Call out deprecations, caveats, or migration notes when the docs surface them.
- If the docs are incomplete, say so and fall back to the best available general knowledge instead of inventing specifics.
What ships with it
3 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.
- 3d ago First seen · 78 lines · 100 tokens per session scan A bda7a1ca42c7
context7 is a skill published in the GitHub repository arvindand/agent-skills (16 stars, last pushed 6d ago), licensed MIT. It adds 100 tokens to every session and 844 once invoked, about $0.0005 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
assistant
Assistant — on any repo, scan README→docs→AGENTS→CONTRIBUTING→PR templates→task runners→devcontainer→CI→configs before code; cite sources; prefer AGENTS.md for agent behavior; portable across Cursor/Copilot/Claude; use agent-toolkit CLI when needed.
design-improvement
WHAT - Browser-grounded iterative design improvement. Consumes design-assessment findings, defines direction, prioritizes safe vs ambiguous changes, implements within existing design system, runs app, captures rendered evidence via browser, reviews and iterates. Reuses evidence model — no new scoring framework.
codeql
CodeQL operational workflow — discover/config, run/inspect, triage SARIF findings (rule/query ID, source→sink, evidence), remediate, re-validate. Distinguishes broad MegaLinter linting from semantic security analysis.
design-assessment
WHAT - Evidence-based design-unit assessment orchestrated by project-assessment. Evaluates visual hierarchy, UX friction, interaction, a11y, responsiveness, design-system compliance, and distinctiveness with severity/confidence evidence citations. Reuses project-assessment-evidence semantics — no second framework.
architecture-diagram
WHAT — Create polished dark-themed architecture diagrams as self-contained HTML+SVG files (inline SVG, CSS styling, PNG/PDF export toolbar). Use when the user asks for system, infrastructure, cloud, security, or network topology diagrams rendered as a shareable visual artifact rather than code.
chrome-devtools
Use Chrome DevTools MCP to control and inspect a live Chrome instance for network, console, performance, rendering, and Deep debugging. Pairs with playwright-cli (deterministic interaction/E2E) — complements, not duplicates.