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-enhancegit 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-enhance)<a href="https://agentmods.dev/commands/mckruz/claude-code-sdlc/sdlc-enhance"><img src="https://agentmods.dev/badge/commands/mckruz/claude-code-sdlc/sdlc-enhance.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.00517 |
| Opus 5 | $0.00000 | $0.00259 |
| Sonnet 5 | $0.00000 | $0.00103 |
| Haiku 4.5 | $0.00000 | $0.00052 |
Grade A, and why
sdlc-enhance 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 5d 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 — 50 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/sdlc-enhance — Generate Narrative Enhancement
Generate stakeholder-friendly narrative companions for SDLC artifacts.
Instructions
-
Read state: Load
.sdlc/state.yamlto determine the current phase. -
Locate artifacts: Find all files in
.sdlc/artifacts/{NN}-{phase-name}/:- Include:
.mdfiles that are technical artifacts - Exclude: files already ending in
.narrative.md - Exclude: artifacts that already have a
.narrative.mdcompanion (unless--forceis specified)
- Include:
-
For each artifact to enhance:
- Spawn
narrative-enhanceragents in parallel (single message with multiple Agent tool calls) — artifacts in the same phase are always independent - Provide each agent with:
- Full path to the source artifact
- Project profile context from
.sdlc/profile.yaml(for audience awareness) - Reference to
references/narrative-patterns.mdfor transformation rules
- The agent writes
{artifact-name}.narrative.mdalongside the source file
- Spawn
-
Report results:
Narrative Enhancement Complete ============================== Enhanced: X artifacts Skipped: Y (already have narratives) Generated: - problem-statement.narrative.md (487 words) - success-criteria.narrative.md (623 words) Coverage: X/Z artifacts have narrative companions
Arguments
- No arguments: enhance all artifacts in the current phase
[path]: enhance a specific artifact (e.g.,/sdlc-enhance .sdlc/artifacts/01-requirements/requirements.md)--force: regenerate narratives even if they already exist--all-phases: enhance artifacts across all completed phases (not just current)
Important
- Narratives are optional — gate checks do NOT require them
- They are recommended before stakeholder reviews and phase transitions
- The
narrative-enhanceragent handles all generation — do not write narratives inline - Narratives are companions, not replacements for technical artifacts
- No activity metrics in client-facing narratives — the
narrative-enhanceragent must never surface velocity, story points, PR/commit counts, lines of code, or "AI productivity" claims, even if a source artifact contains them. Outcomes and quality only (per the delivery standard).
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.
- 5d ago First seen · 50 lines · 0 tokens per session scan A 4f317130baf2
sdlc-enhance 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 517 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
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.
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.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.