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-refreshgit 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.02399 |
| Opus 5 | $0.00000 | $0.01200 |
| Sonnet 5 | $0.00000 | $0.00480 |
| Haiku 4.5 | $0.00000 | $0.00240 |
Grade A, and why
sdlc-refresh 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 — 148 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/sdlc-refresh — Back-Propagate a Built Spec into Its Upstream Artifacts
Traceability normally flows forward (requirement → spec → code). This command runs it backward:
when a spec merges, it surfaces the pre-Build artifacts that spec implies an edit to —
requirements.md, epics.md, feature-brief.md, business-rules.md — so they stop silently
drifting from what actually shipped. It reads as /sdlc-revise inverted: instead of you changing
one artifact and rippling forward, a merged spec proposes the upstream edits and a named human
confirms them.
/sdlc-refresh detect --spec specs/0001-duplicate-claim-409.md
/sdlc-refresh draft --spec specs/0001-duplicate-claim-409.md --draft
/sdlc-refresh apply --spec specs/0001-duplicate-claim-409.md requirements --actor me
/sdlc-refresh status --spec specs/0001-duplicate-claim-409.md
The One Rule holds throughout: the discipline agent drafts the change into a .proposed
copy; a named human decides whether to apply it. No agent ever edits the real artifact.
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/): operate on the given repo.
- Workflow mode (default): look for
-
Detect — review first, draft only on a signal (the divergence-aware default). List the pre-Build upstreams the merged spec traces to (from its
source:frontmatter and any in-vocabulary id in its body). A faithful spec that correctly realizes its upstream lists the upstreams as trace-only (no drift detected) and drafts nothing — the layer never becomes a rubber-stamp:uv run --project ${CLAUDE_PLUGIN_ROOT}/scripts ${CLAUDE_PLUGIN_ROOT}/scripts/audit_artifacts.py refresh detect --spec <spec-path> --state .sdlc/state.yaml- Each row is tagged declared (a written-down link) or coarse (a phase-order guess). Coarse guesses are listed for context and never auto-drafted.
- Zero-candidate honesty: a
source: —, or a non-vocabulary / nonexistent id (REQ-042,FR-999), yields zero candidates and the nudge "no traceable upstream — add an FR/EP/US/BR id tosource:" — never a fabricated guess, never a crash. - Upstreams that already changed after the spec merged are suppressed as already-fresher.
- Pass
--draftto mark all declared upstreams draft-eligible even without a drift signal;--transitive/--include-coarsewiden the set (coarse still never drafts).
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 · 148 lines · 0 tokens per session scan A 5a5e3289521e
sdlc-refresh is a command published in the GitHub repository MCKRUZ/claude-code-sdlc (4 stars, last pushed 5d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,399 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.