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-setupgit 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.03016 |
| Opus 5 | $0.00000 | $0.01508 |
| Sonnet 5 | $0.00000 | $0.00603 |
| Haiku 4.5 | $0.00000 | $0.00302 |
Grade A, and why
sdlc-setup 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 — 204 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/sdlc-setup — Interactive Setup Wizard
Initialize SDLC lifecycle management for a project.
Instructions
Step 1: Check Existing Setup
Look for .sdlc/state.yaml in the current directory.
- If exists: warn the user that SDLC is already initialized. Ask if they want to view status (
/sdlc-status) or re-initialize (destructive — requires confirmation). - If exists but missing
.sdlc/context/directory: offer to upgrade the project structure by creating the missingcontext/layers/directory. This is non-destructive — it only adds new directories, doesn't modify existing state or artifacts. Run:mkdir -p .sdlc/context/layers - If not exists: proceed with setup.
Step 2: Profile Selection
List available profiles from the plugin's profiles/ directory (exclude _schema.yaml):
Present every profile found there to the user. The current built-ins:
- microsoft-enterprise — C#/.NET 8 + Angular 17 + Azure, SOC 2 compliance, 80% coverage minimum, TDD required
- ado-enterprise — microsoft-enterprise's stack on Azure Repos + Azure Pipelines (
platform: azure-devops); same SOC 2 gates, coverage, and TDD bar - ado-enterprise-python — ado-enterprise's Python sibling: FastAPI + SQLAlchemy + React/Redux Toolkit on Azure Repos + Azure Pipelines, Container Apps, SOC 2; prompts PostgreSQL vs Azure SQL at setup
- starter — Minimal profile, no compliance gates, quick start for any stack
- creative-tooling — Python/uv-scripts + pytest for creative pipelines (ComfyUI registry/inventory tooling); 80% coverage, TDD + code/security review required, schema- and cross-reference-integrity evaluation criteria, no compliance frameworks
If the directory listing shows profiles not in this list, present those too (describe them from their
profile.yaml). Ask the user to select a profile.
Step 3: Project Configuration
Ask the user for:
- Project name (default: current directory name)
- Confirm the selected profile settings are appropriate
- If the selected profile is
ado-enterprise-python, also ask: "Database: Azure Database for PostgreSQL (default, idiomatic for Python) or Azure SQL (parity with the .NET enterprise profiles)?" Record the answer — do not edit anything yet (.sdlc/profile.yamldoes not exist until Step 4 runs). The engine choice is advisory metadata: nothing mechanical branches on it (pack selection readsstack.backend.languageandstack.ci_cd.platformonly), the frozen profile carries no checksum guard,stack.database.engineis a free-form string in the profile schema (so Step 9 re-validation passes either value), and Alembic is the migration tool either way.
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 · 204 lines · 0 tokens per session scan A f6950f05d2ae
sdlc-setup is a command published in the GitHub repository MCKRUZ/claude-code-sdlc (4 stars, last pushed 4d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 3,016 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.
constitution
Create or update the project constitution from interactive or provided principle inputs.