Borrowing it
Nothing to install: this file belongs to codeverbojan/claude-code-kickstart. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/codeverbojan/claude-code-kickstart/main/CLAUDE.mdgit clone --depth 1 https://github.com/codeverbojan/claude-code-kickstartWrote 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/instructions/codeverbojan/claude-code-kickstart/claude-md)<a href="https://agentmods.dev/instructions/codeverbojan/claude-code-kickstart/claude-md"><img src="https://agentmods.dev/badge/instructions/codeverbojan/claude-code-kickstart/claude-md/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/instructions/codeverbojan/claude-code-kickstart/claude-md"><img src="https://agentmods.dev/badge/instructions/codeverbojan/claude-code-kickstart/claude-md.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.01335 | $0.01335 |
| Opus 5.5 | $0.00534 | $0.00534 |
| Sonnet 5.5 | $0.00267 | $0.00267 |
| Haiku 4.5 | $0.00134 | $0.00134 |
Grade A, and why
claude-code-kickstart CLAUDE.md 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 2mo 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 — 142 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Be concise. State conclusions first. Skip preamble and filler.
Core loop: gather context → act → verify → repeat.
1. Session Protocol
Start: read primer.md (state, next steps) and gotchas.md (past mistakes).
Pick mode by scope:
- 1–2 files: just do it.
- 3–5 files: state scope, get approval, execute.
- 5+ files: plan mode, phased execution, max 5 files per phase.
End: run /wrap-up before closing the session.
Continuity: prefer claude --continue over fresh sessions. --fork-session
to branch. /compact proactively when context degrades. Don't switch models
mid-session — delegate to sub-agents.
2. Planning
- Plan and build are separate. "Think about this" = plan only, no code.
- If the user gives a plan, execute it. Flag real problems; don't improvise.
- Non-trivial work (3+ steps or architectural decisions): align on tradeoffs before writing code.
- One-word replies ("yes", "do it", "push") = execute, don't restate the plan.
3. Code Quality
- Senior-dev bar. Flawed architecture or duplicated state → propose structural fixes, don't just patch.
- Write human code. No robotic comments or boilerplate.
- Simple and correct beats elaborate and speculative.
- On non-trivial changes, pause once: "is there a cleaner way?"
4. Execution Loop
Non-negotiable workflow for any task beyond a trivial one-liner:
- One task at a time. Batch only closely-related small steps. Never implement task B before task A is fully done (impl + tests + review + fixes).
- Implementation writes the tests. Same context, same turn. Tests are not a follow-up task — they're part of the definition of done.
- Checkpoint reviews in parallel. After each meaningful chunk, launch
review sub-agents concurrently (single message, multiple Agent calls).
Minimum set:
code-reviewer,security-reviewer,test-runner. Addaccessibility-reviewerfor UI work. - Review agents must read the plan first. Every review agent gets the task description, intended behavior, and the list of files touched — not just "review my code". A reviewer without intent can't judge correctness.
- Review scope: bugs, security holes, data leaks, naming problems, inconsistencies, data corruption risks, edge cases, missing tests, race conditions.
- Fix all valid findings before moving on. No "I'll address this in a follow-up." If a finding is invalid, state why in one sentence.
- Never defer quality, testing, or security to the end. Each checkpoint is independently shippable.
- Code understanding: when tracing dependencies, following call graphs, or exploring unfamiliar code, prefer SocratiCode MCP tools (codebase_search, codebase_graph_query) over raw grep for non-trivial searches.
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.
- 2mo ago First seen · 142 lines · 1,335 tokens per session scan A 1817e6955602
claude-code-kickstart CLAUDE.md is an instructions file published in the GitHub repository codeverbojan/claude-code-kickstart (2 stars, last pushed 6mo ago), licensed MIT. It adds 1,335 tokens to every session, about $0.0053 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-31.
Other instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.