Borrowing it
Nothing to install: this file belongs to volodchenkov/claude-sdlc-agents. 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/volodchenkov/claude-sdlc-agents/main/CLAUDE.mdgit clone --depth 1 https://github.com/volodchenkov/claude-sdlc-agentsWrote 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/volodchenkov/claude-sdlc-agents/claude-md)<a href="https://agentmods.dev/instructions/volodchenkov/claude-sdlc-agents/claude-md"><img src="https://agentmods.dev/badge/instructions/volodchenkov/claude-sdlc-agents/claude-md.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.1 | $0.00476 | $0.00476 |
| Opus 5 | $0.00238 | $0.00238 |
| Sonnet 5 | $0.00095 | $0.00095 |
| Haiku 4.5 | $0.00048 | $0.00048 |
Grade A, and why
claude-sdlc-agents 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 8d 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
Claude Code rules for this repo
Release / version bump
.claude-plugin/plugin.json carries the published plugin version. Every PR that touches agents/, skills/, template/, or tools/ MUST bump it. A PR that ships the same version as main is broken — the marketplace will refuse to update for users.
- Default to patch bumps (
0.5.6 → 0.5.7). Prompt rewording, bug fixes, contradiction cleanup — all patch, even if commits are labelledfeat:. - Minor bumps only when the surface grows: a new agent file, a new skill directory, a new MCP integration, a new top-level capability. If unsure between patch and minor, ask — don't guess up.
- Major (
1.x.0) — never without explicit user instruction. - Bump goes in the same commit as the content change. One PR = one commit (unless explicitly split).
PR workflow
- All changes go through a PR. Never push to
maindirectly, never force-push tomain. - One PR can carry multiple themes if they're discovered in the same pass — use one commit per theme for a readable history, but ship one PR.
- Branch naming:
feat/<topic>,fix/<topic>,chore/<topic>. Rename the branch if the scope drifts before opening the PR. - Don't open a PR with the wrong version still in
plugin.json. Check the diff before pushing.
Git safety
- Never
git push --forcetomain, nevergit reset --hardon a shared branch. - Never
--no-verify/--no-gpg-signunless the user explicitly asked. git commit/git pushrequire explicit user OK before each batch — don't chain pushes from one "yes".- If a hook fails, fix the underlying issue and create a NEW commit. Don't
--amendpast hook failures.
Memory hygiene
Project rules live here (in this file). Personal preferences / tone live under ~/.claude/projects/<this>/memory/. If a rule is universal to anyone working on this repo, it belongs in this file, not in private memory.
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.
- 8d ago First seen · 29 lines · 476 tokens per session scan A 9b4363fb39bc
claude-sdlc-agents CLAUDE.md is an instructions file published in the GitHub repository volodchenkov/claude-sdlc-agents (2 stars, last pushed 1mo ago), licensed MIT. It adds 476 tokens to every session, about $0.0024 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-31.
Other instructions, from other repositories
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.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
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).
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
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.
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.