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.
git 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/commands/peterkrueck/claude-code-development-kit/verify)<a href="https://agentmods.dev/commands/peterkrueck/claude-code-development-kit/verify"><img src="https://agentmods.dev/badge/commands/peterkrueck/claude-code-development-kit/verify/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/commands/peterkrueck/claude-code-development-kit/verify"><img src="https://agentmods.dev/badge/commands/peterkrueck/claude-code-development-kit/verify.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00000 | $0.00716 |
| Opus 5.5 | $0.00000 | $0.00286 |
| Sonnet 5.5 | $0.00000 | $0.00143 |
| Haiku 4.5 | $0.00000 | $0.00072 |
Grade C, and why
verify scanned grade C with 2 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.
Hidden instructionshighPrompt injection
Directives inside HTML comments, invisible characters or bidirectional overrides are read by the model and not by the person reviewing the file.
<!-- Database: dry-run the migration on a throwaway/copy, then assert post-state with queries. e.g. apply the migration to a scratch DB, run SELECTs that confirm the schema/data is what you expect, and check rollback wor Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
or `curl -fsS <url>` piped into an assertion for an endpoint. How it starts
The opening of the file, as written. The whole thing — 53 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Verify Command
Run the app or its tests to confirm a change actually works — observed behavior, not just "it compiles." Compiling proves the types line up; it does not prove the feature does what you intended. This command makes you exercise the change and watch the result.
Usage: /verify [what to check]
Pairs with /review-work, which reads the diff for bugs before you run anything — /verify is the run-it-and-watch step that confirms the change behaves.
This is a TEMPLATE
The kit is cross-stack, so this command ships with no live commands — every stack section below is a commented placeholder. Fill in the one(s) your project uses and delete the rest. Discover the real command from the repo (test runner in package.json / Makefile / pyproject.toml / Cargo.toml / a CI workflow, or your docs/ai-context/*.md) rather than hardcoding a guess. If you can't find one, ask the user instead of assuming.
Process
- Identify what changed —
git diff --stat HEAD— and what behavior it should produce. - Pick the verification path for the stack(s) the diff touches (sections below).
- Run it and OBSERVE. A green exit code is necessary, not sufficient — confirm the behavior (right output, right state, right pixels). A test that runs but asserts nothing meaningful has verified nothing.
- On failure, fix and re-run until the observed behavior matches intent. Surface non-trivial fixes to the user.
- Report what you ran, what you observed, and whether it matched intent.
Customize per stack
Uncomment and complete the section(s) that apply to your project. These are EXAMPLES — replace with your repo's real commands.
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 · 53 lines · 0 tokens per session scan C 6fcba9f676c1
verify is a command published in the GitHub repository peterkrueck/Claude-Code-Development-Kit (1,388 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 716 tokens. A static security scan graded it C with 2 findings (hidden instructions, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other commands, from other repositories
prototype
You are building a proof-of-concept for the current Grainulator sprint. Read CLAUDE.md for sprint context and claims.json for existing research claims.
qa-changes
This skill should be used when the user asks to "QA a pull request", "test PR changes", "verify a PR works", "functionally test changes", or when an automated workflow triggers QA validation of code changes. Provides a structured methodology for setting up the environment, exercising changed behavior, and reporting…
verify
Run repository verification using the verification-loop skill.
constraints
A command for defining a project's quality standards through a short interview and a written CONSTRAINTS.md file. It records checks, thresholds, exceptions, and commands for enforcing them.
modernize-transform
Transform one legacy module to the target stack — idiomatic rewrite with behavior-equivalence tests.
test-coverage
Analyze test coverage and identify the highest-value gaps to fill.