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-briefgit 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-brief)<a href="https://agentmods.dev/commands/mckruz/claude-code-sdlc/sdlc-brief"><img src="https://agentmods.dev/badge/commands/mckruz/claude-code-sdlc/sdlc-brief.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.00831 |
| Opus 5 | $0.00000 | $0.00415 |
| Sonnet 5 | $0.00000 | $0.00166 |
| Haiku 4.5 | $0.00000 | $0.00083 |
Grade A, and why
sdlc-brief 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 — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/sdlc-brief — Generate the Discovery Workshop Brief
Run cross-document analysis on the intake corpus and draft the one-page workshop brief, with the human curating what makes the page. Works inside an SDLC project or standalone against any folder of documents.
Instructions
-
Resolve context:
- If
.sdlc/state.yamlexists: workflow mode. Corpus is the locked intake catalog (.sdlc/context/intake/); outputs go to.sdlc/artifacts/00-discovery/. - If not (or
--docs <path>given): standalone mode. Corpus is the given folder; outputs go alongside it. Note in output headers that DOC-NNN IDs are provisional.
- If
-
Ensure intake exists (workflow mode): If the catalog or per-document summaries are missing, stop and tell the human to run document intake first (Phase 0, Step 0c) — the brief is built on the summaries, not raw files. In standalone mode, read the documents directly.
-
Run the analysis: Spawn the
discovery-analystagent to producecontradiction-list.mdandquestion-list.md(templates intemplates/phases/00-discovery/). Skip if both exist and--refreshwas not given. -
Curate with the human:
HITL GATE: Present the analysis to the human using the
AskUserQuestiontool — this is the step that makes the brief curated rather than generated. Ask: (1) Which contradictions make the one page? (show allblocks-outcomeandshapes-designentries with their resolving questions; recommend the top 3-5) (2) Which questions make the one page? (show the workshop-routed list; recommend 8-12 across the agenda blocks; confirm the pre-workshop-routed ones get emailed instead) (3) What are the 3-5 decisions the room must leave with? (4) Logistics: date/time/location, attendees with roles, duration, facilitator.
- Draft the brief: Fill
templates/phases/00-discovery/workshop-brief.mdwith the curated content. Hard rules from the template: one page above the appendices; questions only — no proposed outcomes, metrics, or solutions; every claim carries a DOC-NNN reference.
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 · 66 lines · 0 tokens per session scan A b711fd6c9c0f
sdlc-brief 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 831 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.