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-harnessgit 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-harness)<a href="https://agentmods.dev/commands/mckruz/claude-code-sdlc/sdlc-harness"><img src="https://agentmods.dev/badge/commands/mckruz/claude-code-sdlc/sdlc-harness.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.00638 |
| Opus 5 | $0.00000 | $0.00319 |
| Sonnet 5 | $0.00000 | $0.00128 |
| Haiku 4.5 | $0.00000 | $0.00064 |
Grade A, and why
sdlc-harness 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 — 42 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/sdlc-harness — Install or update the delivery harness
Install (or refresh) the standard-aligned delivery harness in the current repo, independent of a
full /sdlc-setup. Use this to add the harness to a repo that already has .sdlc/, or to pull the
latest harness after a plugin update (the harvest loop).
Instructions
Step 1: Install the harness
Run the installer from the plugin's bundled payload. Idempotent by default — existing files are left in place and reported as SKIPPED.
uv run --project ${CLAUDE_PLUGIN_ROOT}/scripts ${CLAUDE_PLUGIN_ROOT}/scripts/install_harness.py \
--payload ${CLAUDE_PLUGIN_ROOT}/harness --target .
- To overwrite existing harness files with the plugin's current version (e.g. after an update),
add
--force. Review the diff before committing —--forcewill replace local edits.
Step 2: Report
Summarize what was written vs skipped, then remind the user:
- Fill any remaining
{{PLACEHOLDER}}tokens inCLAUDE.mdand the workflows/pipelines. - Prove the rails before trusting them — the shakedown drills in
.github/RAILS.md(the same path holds the ADO guide on azure-devops installs — the pack deliberately overlays it). - Apply branch protection if on GitHub:
bash scripts/rails/apply-branch-protection.sh. On Azure DevOps, configure branch policies instead — needsaz+ theazure-devopsextension:bash scripts/rails/configure-branch-policies.sh --dry-runto preview, then re-run without the flag to apply.
What it installs
CLAUDE.md (governance), specs/spec-template.md, .claude/{settings.json,hooks,agents,skills},
.github/workflows/ (ci, grader, correctness, security, deploy-dev, eval-regression, eval-suite)
RAILS.md,.github/{profile/rubrics,rulesets,CODEOWNERS,eval-bypasses.md},scripts/rails/,eval-datasets/,prompts/, andinfra/. Onplatform: azure-devopsprofiles the platform surface is realized as.azuredevops/pipelines/(the same rails as Azure Pipelines) and.azuredevops/rails/(rubrics +branch-policies.json— build-validation and required-reviewer policies standing in for rulesets and CODEOWNERS);.github/RAILS.mdstill carries the operator guide. See.claude/agents/README.mdfor the agent/skill catalog and the on-demand menu.
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 · 42 lines · 0 tokens per session scan A de924ffd710b
sdlc-harness 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 638 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
template
Manage issue templates for streamlined issue creation.
sync-linear
Sync current work with Linear ticket status.
add-note
Add an internal or external note to a ConnectWise PSA ticket.
fest-show
Show festival progression (in-progress tasks, roadmap, and dependency view).
dispatcher
Pick the next-best repo to work on across the portfolio — rank free repos, recommend one, claim its lease atomically, and route to the entry command.
clarify
Walk through inbox items applying the GTD decision tree. Usage: /gtd:clarify [--id gtd-xxx].