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 commands/mckruz/claude-code-mastery/sdlc-setupgit clone --depth 1 https://github.com/MCKRUZ/claude-code-masteryWhat 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.00019 | $0.00594 |
| Opus 5 | $0.00010 | $0.00297 |
| Sonnet 5 | $0.00004 | $0.00119 |
| Haiku 4.5 | $0.00002 | $0.00059 |
Grade A, and why
/sdlc-setup 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 3d 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 — 81 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/sdlc-setup - Interactive Setup Wizard
Initialize SDLC lifecycle management for a project.
Workflow
Step 1: Check Existing Setup
Look for .sdlc/state.yaml in the current directory.
- If exists: warn the user that SDLC is already initialized. Ask if they want to view status (
/sdlc) or re-initialize (destructive -- requires confirmation). - If not exists: proceed with setup.
Step 2: Profile Selection
List available profiles:
- microsoft-enterprise — C#/.NET 8 + Angular 17 + Azure, SOC 2 compliance, 80% coverage minimum, TDD required
- starter — Minimal profile, no compliance gates, quick start for any stack
Ask the user to select a profile.
Step 3: Project Configuration
Ask the user for:
- Project name (default: current directory name)
- Confirm the selected profile settings are appropriate
Step 4: Initialize .sdlc/
Create the following directory structure:
.sdlc/
state.yaml # Phase tracking (Phase 0: Discovery active)
profile.yaml # Frozen copy of selected profile
constitution.md # Project constitution
artifacts/ # Per-phase artifact directories (00-09)
If an init script is available (e.g., init_project.py), run it:
python scripts/init_project.py \
--profile profiles/<selected-profile>/profile.yaml \
--target . \
--name "<project-name>"
Otherwise, create the directory structure manually.
Step 5: Update CLAUDE.md / Project Instructions
Read the profile's claude-md-template.md and append its contents to the project's instruction file:
- If project instructions exist: append the SDLC section
- If they don't exist: create with the SDLC section
Step 6: Confirmation
Display:
SDLC initialized successfully!
Profile: <profile-id>
Phase: 0 - Discovery (active)
Artifacts: .sdlc/artifacts/00-discovery/
Next steps:
1. Run /sdlc to see Phase 0 guidance
2. Create your problem statement in .sdlc/artifacts/00-discovery/problem-statement.md
3. Check exit criteria when ready
4. Advance to Phase 1 when criteria are met
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.
- 3d ago First seen · 81 lines · 19 tokens per session scan A 39ef008075cf
/sdlc-setup is a command published in the GitHub repository MCKRUZ/claude-code-mastery (11 stars, last pushed 4mo ago), licensed MIT. It adds 19 tokens to every session and 594 once invoked, about $0.0001 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-30.
Other commands, from other repositories
claude-md-migrate
Rewrite a bloated or stale CLAUDE.md into a lean, verified "map, not wishes" file — nothing invented, hard rules preserved verbatim.
claude-md-new
Scaffold a CLAUDE.md for this repo from battle-tested templates, filled in with the project's real commands.
claude-md-audit
Grade this repo's CLAUDE.md / AGENTS.md (0–100) and return a worst-first fix list.
review
请从风险、回归、测试遗漏和可读性四个角度 review 当前变更。.
explain
请解释当前文件或目录的核心结构，并指出我下一步应该看哪里。.
fix
请先定位根因，再给出最小修改方案，最后说明验证方式。.