Claude Code Development Kit is a starter workflow that gives Claude Code project context, working notes, verification commands, review commands, and hooks for maintaining them across sessions. It is for beginners and intermediate users building applications or side projects who want Claude Code to understand the codebase and check its work. The catalogue entries are the kit's skills and commands.
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 peterkrueck/Claude-Code-Development-Kit --skill context7-guidancegit clone --depth 1 https://github.com/peterkrueck/Claude-Code-Development-KitWrote 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/peterkrueck/claude-code-development-kit/context7-guidance)<a href="https://agentmods.dev/skills/peterkrueck/claude-code-development-kit/context7-guidance"><img src="https://agentmods.dev/badge/skills/peterkrueck/claude-code-development-kit/context7-guidance/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/peterkrueck/claude-code-development-kit/context7-guidance"><img src="https://agentmods.dev/badge/skills/peterkrueck/claude-code-development-kit/context7-guidance.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 29 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00086 | $0.00575 |
| Opus 5.5 | $0.00034 | $0.00230 |
| Sonnet 5.5 | $0.00017 | $0.00115 |
| Haiku 4.5 | $0.00009 | $0.00057 |
Grade A, and why
context7-guidance 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 1mo 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 — 37 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Context7 Guidance — Current Docs Over Training Data
The kit ships the Context7 plugin permission so you can pull current documentation at the version the project actually uses. Training data drifts: APIs get deprecated, defaults change, config keys get renamed. When the question is about a real library, fetch the docs — don't answer from memory.
When to Use
Reach for Context7 when the user:
- Names a specific library, framework, SDK, or cloud service (common web frameworks, APIs, and cloud services — even ones you "know")
- Asks a setup or configuration question ("how do I wire up X middleware?")
- Plans a version migration ("upgrading to vN — what changed?")
- Is debugging library-specific behavior (an error, a deprecation, an unexpected default)
- Wants code that calls a third-party API — verify the signature before writing it
When NOT to use it: general programming concepts, refactoring your own code, debugging your own business logic, writing a script from scratch, or code review of non-library logic. Context7 is for external surfaces, not your codebase.
How to Fetch
- Resolve the library ID. Call
resolve-library-idwith the library name and pass the user's full question as the query — it sharpens the ranking. - Pick the best match. Prefer an exact name match and the official/primary package over community forks. If the user named a version, prefer the version-specific ID.
- Query the docs. Call
query-docswith the chosen library ID and the user's specific question (not a single keyword). - Answer from the result. Use the fetched docs, include relevant examples, and cite the version when it matters.
If the tools aren't directly callable, load them first via ToolSearch (select:mcp__context7__resolve-library-id,mcp__context7__query-docs) — don't skip verification just because they weren't preloaded.
Guidelines
- Pass the full question, not one word — it improves relevance at both steps.
- Be version-aware — when the user mentions a version, carry it into the resolve step.
- Prefer official sources when several matches exist.
- Fall back to web search only if Context7 has no coverage for that library.
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.
- 1mo ago First seen · 37 lines · 86 tokens per session scan A 87990e6fbc06
context7-guidance is a skill published in the GitHub repository peterkrueck/Claude-Code-Development-Kit (1,388 stars, last pushed 3mo ago), licensed MIT. It adds 86 tokens to every session and 575 once invoked, about $0.0003 per session on Opus 5.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
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…
next-cache-components-optimizer
Optimize the meaningful UI available immediately from a Next.js route on an initial load (hard navigation) or named client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route and entry point at a time; the shipped test then guards…