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-retrogit 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-retro)<a href="https://agentmods.dev/commands/mckruz/claude-code-sdlc/sdlc-retro"><img src="https://agentmods.dev/badge/commands/mckruz/claude-code-sdlc/sdlc-retro.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.01428 |
| Opus 5 | $0.00000 | $0.00714 |
| Sonnet 5 | $0.00000 | $0.00286 |
| Haiku 4.5 | $0.00000 | $0.00143 |
Grade A, and why
sdlc-retro 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 — 94 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/sdlc-retro — Cross-Ledger Retro Roll-up
Read across the three advisory ledgers at once and surface what keeps happening — the retro question the per-round commands can't answer on their own. It reports four patterns:
- Recurring findings — a
(category, target)group seen in >= 2 distinct review rounds is a candidate for a permanent check (this is how "findings become new checks"). - Repeat-stale artifacts — per downstream artifact, how many times it was dispositioned for staleness, and whether it is stale right now.
- Refresh funnel — per merged spec and by upstream stem: candidates → drifted → refreshed → rejected → still open. This doubles as the tuning signal for the divergence heuristic.
- Disposition debt rollup — combined honest-counting debt across all three ledgers, each line naming its source.
This is a sibling to /sdlc-audit-artifacts (freshness now) and /sdlc-audit (gate
effectiveness). This command reads the accumulated history and reports the recurring shape of it.
It reads three ledgers, computes nothing about people, and never blocks.
Instructions
-
Resolve mode and repo root:
- Workflow mode (default): look for
.sdlc/state.yaml. Pass--state .sdlc/state.yaml. If not found, tell the user to run/sdlc-setupfirst. - Standalone mode (
--repo <path>, or no.sdlc/found): run against any repo with a.sdlc/directory. The roll-up is only as deep as the ledgers in that repo — with a thin or missing ledger, each section degrades to "no data" (never a fabricated zero), and the missing context is noted by that "no data" line rather than guessed at.
- Workflow mode (default): look for
-
Run the roll-up (read-only — writes nothing, ever):
uv run --project ${CLAUDE_PLUGIN_ROOT}/scripts ${CLAUDE_PLUGIN_ROOT}/scripts/retro_report.py --state .sdlc/state.yamlIn standalone mode point it at any repo instead:
uv run --project ${CLAUDE_PLUGIN_ROOT}/scripts ${CLAUDE_PLUGIN_ROOT}/scripts/retro_report.py --repo /path/to/repo
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 · 94 lines · 0 tokens per session scan A a7b9810b6907
sdlc-retro 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,428 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
template
Manage issue templates for streamlined issue creation.
project-recap
Generate a visual project recap for context switching.
guide
You are a triage agent who continuously prioritizes loom:issue issues by applying loom:urgent to the top 3 priorities.
sync-linear
Sync current work with Linear ticket status.
add-note
Add an internal or external note to a ConnectWise PSA ticket.
fest-show
Show festival progression (in-progress tasks, roadmap, and dependency view).