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-experiencegit 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-experience)<a href="https://agentmods.dev/commands/mckruz/claude-code-sdlc/sdlc-experience"><img src="https://agentmods.dev/badge/commands/mckruz/claude-code-sdlc/sdlc-experience.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.01321 |
| Opus 5 | $0.00000 | $0.00660 |
| Sonnet 5 | $0.00000 | $0.00264 |
| Haiku 4.5 | $0.00000 | $0.00132 |
Grade A, and why
sdlc-experience 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 — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/sdlc-experience — Author the Channel-Shaped Experience for a Surface
Author the craft of a surface — the user journey, the surface layout, and the channel interaction
spec — for one channel-bound spec. This is the author beat between /sdlc-feature (which
decomposes) and /sdlc-channel (which binds): decompose → author → bind. It routes by the
feature's channel to the right designer — ag-ui to the visual-designer, voice/chat to the
conversation-designer — and is interview-driven like /sdlc-coach: the designer assesses what's
there, asks focused questions, and drafts as answers arrive. Design proposes; a named human
decides. Works inside an SDLC project or standalone.
Instructions
-
Resolve context:
- Workflow mode (default):
.sdlc/state.yamlexists. Read thefeature-brief.mdrow (or the spec'schannel:field) for the surface being designed; artifacts land in.sdlc/artifacts/02-design/experience/. - Standalone mode (
--repo <path>, or no.sdlc/found): operate on the given repo with provisional context; write to--output(default alongside the repo) and note the missing context in the artifact headers.
- Workflow mode (default):
-
Determine the channel and load its descriptor: Take the channel from
--channel, the target spec'schannel:field, or the feature-brief row (ask if none is set). Readchannels/<channel>.yaml— its Acceptance Dimensions and Interaction Contract drive the interaction spec. If no descriptor exists for the channel, tell the human to add one (channels/_template.yaml→validate_channel.py) before authoring. -
Route to the right designer:
ag-ui(and other screen-based surfaces) → spawn thevisual-designeragent (Design / web); itssurface-layout.mdholds screens and itschannel-interaction-spec.mdis the AG-UI event contract, co-authored with Engineering.voiceorchat→ spawn theconversation-designeragent (Design / voice + chat); itssurface-layout.mdis the turn-by-turn script (voice) or message flow (chat) and its interaction spec is the turn / barge-in / readback (voice) or threading / escalation (chat) contract.
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 · 85 lines · 0 tokens per session scan A 6932daa1bc20
sdlc-experience 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,321 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
ui-flow-review
Review menus, HUD, navigation, and player flow from a UX perspective.
template-ui
Design a Sent template-builder interface.
responsive-design-specialist
Use when a layout breaks between sizes. Arbitrary breakpoints, type that does not scale, images that blow out the grid, or a desktop design retrofitted onto mobile.
study
Runtime entry point for extracting design DNA from a live URL, screenshot, or reference site. Part of the Discovery lifecycle phase.
4-generate
Run Stage 4 of the design system skill generation pipeline: parallel skill file generation.
audit-ux
Whole-repo adversarial UX audit of the shipped user surfaces -> docs/audits/ux-audit- .md.