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-phase-reportgit 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-phase-report)<a href="https://agentmods.dev/commands/mckruz/claude-code-sdlc/sdlc-phase-report"><img src="https://agentmods.dev/badge/commands/mckruz/claude-code-sdlc/sdlc-phase-report.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.00826 |
| Opus 5 | $0.00000 | $0.00413 |
| Sonnet 5 | $0.00000 | $0.00165 |
| Haiku 4.5 | $0.00000 | $0.00083 |
Grade A, and why
sdlc-phase-report 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 — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/sdlc-phase-report — Generate Phase HTML Report
Render all artifacts for the current (or specified) phase into a self-contained HTML report for stakeholder review.
Instructions
-
Locate state file: Look for
.sdlc/state.yamlin the current project directory. If not found, tell the user to run/sdlc-setupfirst. -
Determine target phase:
- No argument → use
current_phasefrom state file - Phase-id argument (e.g.,
/sdlc-phase-report 2) → use that phase id - Validate the id against the registry (
0,1,2,3,build,7,8,9,close)
- No argument → use
-
Run report generator:
For a single phase:
uv run --project ${CLAUDE_PLUGIN_ROOT}/scripts ${CLAUDE_PLUGIN_ROOT}/scripts/generate_phase_report.py \ --state .sdlc/state.yaml \ --phase <phase-id>The output defaults to
.sdlc/reports/<slug>-report.html, where<slug>is the phase's registry slug (e.g.00-discovery-report.html,build-report.html); pass--outputonly to override it.For all phases (produces individual reports and
index.html):uv run --project ${CLAUDE_PLUGIN_ROOT}/scripts ${CLAUDE_PLUGIN_ROOT}/scripts/generate_phase_report.py \ --state .sdlc/state.yaml \ --allWhere
${CLAUDE_PLUGIN_ROOT}is the environment variable Claude Code sets to the plugin's install directory. -
Handle output:
- On success: 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 # Linux - On failure: display the error from the script and suggest checking that artifact files exist
- On success: automatically open the report in the user's default browser:
-
Update project index: After generating the phase report, create or update
.sdlc/reports/index.html:- If
index.htmldoes not exist: create it with project header, mission, constitution link, and all 9 phases (0, 1, 2, 3, build, 7, 8, 9, close) showing current status - If
index.htmlexists: update the phase status badges, dates, and report links to reflect current state - The index is the single entry point for all project documentation
- 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.
- 4d ago First seen · 72 lines · 0 tokens per session scan A e9808d5ba108
sdlc-phase-report 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 826 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
organize-files
Organize and rename files based on content analysis.
brand-generate
Generate an on-brand document from a saved Brand Profile.
tree
Show file tree with sync status indicators showing which files are indexed, modified, new, or deleted.
cti-report
Render case deliverables — relationship graph (PNG/SVG/Mermaid) and a polished PDF/DOCX assessment. Usage: /cti-report [--graph|--pdf].
ppt-image2-editable-rebuild
Rebuild image2 or imagegen reference slides as editable PowerPoint decks.
convert
Convert a file to Markdown using markitdown.