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 agentmods add instructions/mckruz/claude-code-sdlc/claude-mdgit clone --depth 1 https://github.com/MCKRUZ/claude-code-sdlcWrote 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/mckruz/claude-code-sdlc/claude-md)<a href="https://agentmods.dev/instructions/mckruz/claude-code-sdlc/claude-md"><img src="https://agentmods.dev/badge/instructions/mckruz/claude-code-sdlc/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 | $0.04345 | $0.04345 |
| Opus 5 | $0.02173 | $0.02173 |
| Sonnet 5 | $0.00869 | $0.00869 |
| Haiku 4.5 | $0.00434 | $0.00434 |
Grade A, and why
claude-code-sdlc 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 4d 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 — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.
claude-code-sdlc — Development Instructions
What This Is
A Claude Code plugin that orchestrates the full SDLC lifecycle using company-configurable profiles. It makes the AI-SDLC methodology executable within Claude Code.
Architecture
plugin.json— Plugin manifest (entry point for Claude Code)SKILL.md— Main skill definition (loaded when plugin activates)commands/— 26 slash commands (/sdlc,/sdlc-setup,/sdlc-status,/sdlc-next,/sdlc-gate,/sdlc-enhance,/sdlc-coach,/sdlc-review,/sdlc-intake,/sdlc-brief,/sdlc-spec,/sdlc-phase-report,/sdlc-audit,/sdlc-feature,/sdlc-experience,/sdlc-data,/sdlc-rules,/sdlc-channel,/sdlc-evals,/sdlc-harness,/sdlc-upgrade,/sdlc-revise,/sdlc-audit-artifacts,/sdlc-version,/sdlc-refresh,/sdlc-retro)agents/— 13 agents (orchestrator, requirements-analyst, compliance-checker, section-evaluator, narrative-enhancer, gate-repair, multi-reviewer, discovery-analyst, feature-architect, visual-designer, conversation-designer, data-analyst, bizreq-analyst)channels/— Cross-profile channel descriptor library (_schema.yaml,ag-ui.yaml,voice.yaml,chat.yaml) — the delivery-surface vocabulary the channel layer readsprofiles/— Company/stack YAML configs with compliance gatesphases/— Phase definitions (9 phases: 0, 1, 2, 3 Foundation, build loop, 7, 8, 9, close). The 4/5/6 gap is intentional — the batch Implementation/Quality/Testing phases are replaced by the continuous Build loop. Phase identity/ordering is owned byscripts/phase_model.pyreadingphases/phase-registry.yaml.references/— Progressive disclosure docs (loaded on-demand)templates/— Artifact templates copied to target projectsscripts/— Python automation (uv runtime)hooks/— PowerShell hooks for session/phase context injection
Conventions
- Profile YAML validated against
profiles/_schema.yaml - Phase definitions use RFC 2119 keywords (MUST/SHOULD/MAY)
- Scripts use Python 3.12+ via uv
- State tracked in target project's
.sdlc/state.yaml
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.
- 4d ago First seen · 97 lines · 4,345 tokens per session scan A 182805b2ae04
claude-code-sdlc CLAUDE.md is an instructions file published in the GitHub repository MCKRUZ/claude-code-sdlc (4 stars, last pushed 6d ago), licensed MIT. It adds 4,345 tokens to every session, about $0.0217 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
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).
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.
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.
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 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).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.