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/sdlcgit clone --depth 1 https://github.com/MCKRUZ/claude-code-sdlcWhat 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.00724 |
| Opus 5 | $0.00000 | $0.00362 |
| Sonnet 5 | $0.00000 | $0.00145 |
| Haiku 4.5 | $0.00000 | $0.00072 |
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 2d 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 — 69 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.
Instructions
-
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: Present to the user:
Header
Phase {N}: {Name} Profile: {profile_id}Team & RACI (this phase)
Read
references/team-model.mdfrom the plugin directory and find the entry keyed by the current phase id. Render a short block: which disciplines are active this phase and their per-phase RACI (Responsible / Accountable / Consulted / Informed). This tells each seat — Product, Data, Design, Engineering, Bizreq — where it owns work vs. where it advises.- Degrade gracefully: if
references/team-model.mdis absent, or has no entry for this phase, skip this subsection silently and continue — do not error or emit a placeholder.
Purpose
One-line description of this phase's goal.
Resolved Questions from Previous Phase
Check the previous phase's handoff document (e.g.,
phase1-handoff.mdwhen in Phase 1) for a "Resolved Questions" section. If it exists, list the resolved questions as context — these are confirmed inputs that MUST inform the current phase's artifacts. If no resolved questions section exists, note that and move on.What to Do Next
Based on the phase workflow steps, current artifact state, and resolved questions:
- List the next actionable step
- Reference the specific skill/command to use
- Note which resolved questions feed into which artifacts
- Example: "Write
requirements.mdusing resolved questions RQ-1 through RQ-3 as inputs"
- Degrade gracefully: if
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.
- 2d ago First seen · 69 lines · 0 tokens per session scan A 44df2ce75b3b
sdlc is a command published in the GitHub repository MCKRUZ/claude-code-sdlc (4 stars, last pushed 4d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 724 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
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.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
constitution
Create or update the project constitution from interactive or provided principle inputs.
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.