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/sdlcgit 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.00028 | $0.00625 |
| Opus 5 | $0.00014 | $0.00313 |
| Sonnet 5 | $0.00006 | $0.00125 |
| Haiku 4.5 | $0.00003 | $0.00063 |
Grade A, and why
/sdlc 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 — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/sdlc - Phase Guidance
Show guidance for the current SDLC phase including what to do, which skills to use, and what artifacts to produce.
Workflow
-
Locate state file: Look for
.sdlc/state.yamlin the current project directory. If not found, tell the user to run/sdlc-setupfirst and exit. -
Read state: Load
.sdlc/state.yamlto getcurrent_phase. -
Load phase definition: Read the phase definition file from
phases/XX-phasename.md(where XX is the zero-padded phase number). -
Load profile: Read
.sdlc/profile.yamlto get stack and quality configuration. -
Display phase context:
Header
Phase {N}: {Name} Profile: {profile_id}Purpose
One-line description of this phase's goal.
What to Do Next
Based on the phase workflow steps and current artifact state:
- List the next actionable step
- Reference the specific skill/command to use
- Example: "Run
/planto decompose your problem statement into requirements"
Required Artifacts
List artifacts needed to pass exit gates, with status:
- artifact.md (exists, 1.2KB)
- other-artifact.md (missing)
Skills to Use
List primary and secondary skills for this phase with brief description.
Exit Criteria
Summarize what must be true to advance (from phase definition's exit criteria).
Quick Commands
/sdlc-setup - Initialize SDLC for a project -
Compliance callout: If the profile has compliance frameworks, note any compliance-specific requirements for this phase.
-
Be concise. The phase definition file has full details -- this command shows the actionable summary, not the full document.
Arguments
- No arguments: show guidance for current phase
<phase-number>: show guidance for a specific phase (e.g.,/sdlc 3)
SDLC Sub-Commands
The full SDLC lifecycle includes these additional sub-commands (not yet ported to Cursor -- available in Claude Code):
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 · 73 lines · 28 tokens per session scan A 8940a53023a3
/sdlc is a command published in the GitHub repository MCKRUZ/claude-code-mastery (11 stars, last pushed 4mo ago), licensed MIT. It adds 28 tokens to every session and 625 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
请先定位根因，再给出最小修改方案，最后说明验证方式。.