sdlc-harness

sdlc-harness is a command for coding agents from MCKRUZ/claude-code-sdlc. It costs 0 tokens per session (638 once invoked), scanned A, original, MIT.

A command that installs or updates a software-delivery checklist and workflow in a repository that already has an .sdlc folder.

In plain words
What is it for?
Use it to add the delivery harness to an existing project or refresh it after an update. It also points out remaining placeholders and verification drills to complete.
Why use it?
It provides the shared delivery files without requiring the repository's full setup process, while reporting which files were added or left unchanged.

Command

Installs and runs on its own, but its text points at files inside its plugin — anything it tells you to read at a ${CLAUDE_PLUGIN_ROOT} path is only there once the plugin is installed. Installing the plugin gets both.

Part of the claude-code-sdlc plugin — 9 skills, 28 commands, 20 agents shipped together

Install

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.

agentmods
npx agentmods add commands/mckruz/claude-code-sdlc/sdlc-harness
Clone the repo
git clone --depth 1 https://github.com/MCKRUZ/claude-code-sdlc

Or install claude-code-sdlc, the plugin that ships this one along with the rest of its 9 skills, 28 commands, 20 agents.

Wrote 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.

agentmods badge for sdlc-harness

README.md
[![agentmods](https://agentmods.dev/badge/commands/mckruz/claude-code-sdlc/sdlc-harness.svg)](https://agentmods.dev/commands/mckruz/claude-code-sdlc/sdlc-harness)
Your own site
<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>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 638 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce 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

Measured 4d ago against content hash de924ffd710b, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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.

commands/sdlc-harness.md · 42 lines

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 — --force will replace local edits.

Step 2: Report

Summarize what was written vs skipped, then remind the user:

  • Fill any remaining {{PLACEHOLDER}} tokens in CLAUDE.md and 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 — needs az + the azure-devops extension: bash scripts/rails/configure-branch-policies.sh --dry-run to 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/, and infra/. On platform: azure-devops profiles 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.md still carries the operator guide. See .claude/agents/README.md for the agent/skill catalog and the on-demand menu.

Read the full file on GitHub · 42 lines

Changes

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.

  1. 4d ago First seen · 42 lines · 0 tokens per session scan A de924ffd710b

Subscribe to this mod's changes

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.