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-gategit 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-gate)<a href="https://agentmods.dev/commands/mckruz/claude-code-sdlc/sdlc-gate"><img src="https://agentmods.dev/badge/commands/mckruz/claude-code-sdlc/sdlc-gate.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.01108 |
| Opus 5 | $0.00000 | $0.00554 |
| Sonnet 5 | $0.00000 | $0.00222 |
| Haiku 4.5 | $0.00000 | $0.00111 |
Grade A, and why
sdlc-gate 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 — 75 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/sdlc-gate — Run Exit Criteria Check
Run the 7-gate validation system for the current (or specified) SDLC phase without advancing.
Instructions
-
Locate state file: Look for
.sdlc/state.yamlin the current project directory. If not found, tell the user to run/sdlc-setupfirst. -
Read state: Load
.sdlc/state.yamlto determine the current phase. -
Check visual report exists: Before running gates, verify that the phase visual report exists at
.sdlc/reports/<slug>-visual.html, where<slug>is the phase's registry slug (e.g.00-discovery-visual.html,build-visual.html). Also verify that artifact sub-pages exist and are linked from the main report.- If the visual report is missing: STOP. Tell the user: "The phase visual report has not been generated yet. The visual report is the primary stakeholder review artifact and must exist before running gate checks. Generate it now?" If yes, generate the visual report with artifact sub-pages first, then proceed with gates.
- If sub-pages are missing: WARN but proceed. Note which artifacts lack sub-pages in the gate output.
-
Run gate checks: Execute the gate checker:
uv run --project ${CLAUDE_PLUGIN_ROOT}/scripts ${CLAUDE_PLUGIN_ROOT}/scripts/check_gates.py --state .sdlc/state.yamlOptionally specify a phase:
--phase <N> -
Display results: Show each gate result with:
- Gate name (G1-integrity, G2-completeness, G3-metrics, G4-compliance, G5-consistency, G6-quality, G7-exit-criteria)
- PASS / FAIL / MANUAL status
- Severity (MUST / SHOULD / MAY)
- Details on what passed or failed
-
Generate phase report: Always generate the HTML report after running gates, regardless of pass/fail status:
uv run --project ${CLAUDE_PLUGIN_ROOT}/scripts ${CLAUDE_PLUGIN_ROOT}/scripts/generate_phase_report.py \ --state .sdlc/state.yaml --phase <phase-number>The script writes
.sdlc/reports/<slug>-report.html(registry slug, e.g.00-discovery-report.html,build-report.html). After generating, automatically open the report in the user's default browser:start .sdlc/reports/<slug>-report.html # Windows open .sdlc/reports/<slug>-report.html # macOS xdg-open .sdlc/reports/<slug>-report.html # LinuxThis is the artifact stakeholders review before the manual gate sign-off.
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 · 75 lines · 0 tokens per session scan A 4040f16b274d
sdlc-gate is a command published in the GitHub repository MCKRUZ/claude-code-sdlc (4 stars, last pushed 6d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,108 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.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
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.