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-sdlc/sdlc-coachgit 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/commands/mckruz/claude-code-sdlc/sdlc-coach)<a href="https://agentmods.dev/commands/mckruz/claude-code-sdlc/sdlc-coach"><img src="https://agentmods.dev/badge/commands/mckruz/claude-code-sdlc/sdlc-coach.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.00000 | $0.00555 |
| Opus 5 | $0.00000 | $0.00278 |
| Sonnet 5 | $0.00000 | $0.00111 |
| Haiku 4.5 | $0.00000 | $0.00056 |
Grade A, and why
sdlc-coach 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 — 51 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/sdlc-coach — Interactive Phase Coaching
Start or continue a coaching conversation for the current SDLC phase. Coaching mode uses adaptive dialogue instead of rigid step lists to guide the user through phase requirements.
Instructions
-
Read state: Load
.sdlc/state.yamlto determine the current phase. -
Assess state: Read all artifacts in
.sdlc/artifacts/{NN}-{phase-name}/:- Which artifacts exist?
- Which are complete vs. still containing placeholders?
- What decisions remain unmade?
-
Load context:
- Read
references/conversational-coaching.mdfor coaching patterns and diagnostic questions - Read frozen layers from
.sdlc/context/layers/for prior phase context - Read the phase definition from
phases/{NN}-{phase-name}.mdfor requirements
- Read
-
Begin coaching dialogue based on state:
No artifacts exist → Opening mode:
- Greet with phase goal in one sentence
- Ask the first 2-3 diagnostic questions from the phase's "Opening" section
- Wait for responses before generating any artifacts
Some artifacts exist → Progress mode:
- Acknowledge what's done ("I see your problem statement and constraints are in place")
- Identify the most important gap
- Ask targeted questions from the phase's "Progress Check" section
All required artifacts exist → Ready mode:
- Confirm all artifacts are present
- Ask the "Ready Check" questions to validate confidence
- Suggest running
/sdlc-gatewhen the user is satisfied
-
Respond adaptively to each user interaction:
- User provides information → generate or update the relevant artifact, then ask the next question
- User asks a question → answer from phase context and profile, then guide back to the gap
- User is stuck → offer 2-3 concrete suggestions based on the state assessment
- User wants to skip ahead → warn about gate requirements, explain what's needed
-
Track through artifacts: The coaching conversation itself is ephemeral — artifacts are the record. After each significant exchange, update the relevant artifact so progress is preserved across sessions.
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 · 51 lines · 0 tokens per session scan A 3bf66e5fed89
sdlc-coach is a command published in the GitHub repository MCKRUZ/claude-code-sdlc (4 stars, last pushed 7d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 555 tokens. 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 commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.