Borrowing it
Nothing to install: this file belongs to cloudnative-co/claude-code-starter-kit. 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/cloudnative-co/claude-code-starter-kit/main/.github/instructions/review.instructions.mdgit clone --depth 1 https://github.com/cloudnative-co/claude-code-starter-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/instructions/cloudnative-co/claude-code-starter-kit/review)<a href="https://agentmods.dev/instructions/cloudnative-co/claude-code-starter-kit/review"><img src="https://agentmods.dev/badge/instructions/cloudnative-co/claude-code-starter-kit/review/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/cloudnative-co/claude-code-starter-kit/review"><img src="https://agentmods.dev/badge/instructions/cloudnative-co/claude-code-starter-kit/review.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.00240 | $0.00240 |
| Opus 5.5 | $0.00096 | $0.00096 |
| Sonnet 5.5 | $0.00048 | $0.00048 |
| Haiku 4.5 | $0.00024 | $0.00024 |
Grade A, and why
claude-code-starter-kit review.instructions.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.
What it actually says
When reviewing changes in this repository, explicitly check upgrade-path coverage in addition to fresh-install behavior.
If a pull request adds or changes a feature flag, setup prompt, generated file, profile default, hook, command, settings key, or any other user-visible setup behavior, review whether existing installs are upgraded correctly through setup.sh --update and /update-kit.
Look for cases where a new key is added for fresh installs but older saved config, manifests, or deployed files would silently miss the new behavior. Missing keys on older installs should receive the intended default for that profile, but explicit user choices that already exist must not be overwritten.
Also review whether user-facing documentation was updated in the same pull request when needed. Check for missing updates to:
CHANGELOG.mdfor user-visible behavior changes, new defaults, upgrade behavior changes, or new commandsREADME.mdandREADME.en.mdfor setup flow, defaults, CLI flags, or prerequisites- files under
docs/when configuration mapping, feature behavior, or upgrade behavior changed
If these update-path or documentation concerns are missing, call them out as review findings instead of assuming they can be handled later.
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 · 14 lines · 240 tokens per session scan A 9b836a39c469
claude-code-starter-kit review.instructions.md is an instructions file published in the GitHub repository cloudnative-co/claude-code-starter-kit (154 stars, last pushed 18d ago), licensed MIT. It adds 240 tokens to every session, about $0.0010 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 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.