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-upgradegit 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-upgrade)<a href="https://agentmods.dev/commands/mckruz/claude-code-sdlc/sdlc-upgrade"><img src="https://agentmods.dev/badge/commands/mckruz/claude-code-sdlc/sdlc-upgrade.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.01324 |
| Opus 5 | $0.00000 | $0.00662 |
| Sonnet 5 | $0.00000 | $0.00265 |
| Haiku 4.5 | $0.00000 | $0.00132 |
Grade A, and why
sdlc-upgrade 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 — 90 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/sdlc-upgrade — Bring an installed harness forward safely
Upgrade a repo's installed delivery harness to the plugin's current version using the install
receipt (.claude/harness-manifest.json). Unlike install_harness.py --force, this never
clobbers a repo's adaptations: files still factory-original are brought forward, adapted files
are left alone, and files changed on both sides are surfaced for a deliberate merge.
Instructions
Step 1: Dry-run the upgrade
Always dry-run first. Pass the same profile that was used at install (.sdlc/profile.yaml for
repos set up via /sdlc-setup; omit --profile only for core-only installs) — a different
profile makes that profile's pack files misreport as RETIRED.
uv run --project ${CLAUDE_PLUGIN_ROOT}/scripts ${CLAUDE_PLUGIN_ROOT}/scripts/upgrade_harness.py \
--payload ${CLAUDE_PLUGIN_ROOT}/harness --target . --profile .sdlc/profile.yaml
Step 2: Read the report to the user
Explain the classification groups in plain terms before touching anything:
| Label | Meaning | On --apply |
|---|---|---|
IDENTICAL |
already matches the new version | manifest entry refreshed |
UPDATE |
factory-original here, improved upstream | replaced with the new version |
ADAPTED |
this repo changed it, upstream didn't | left alone |
CONFLICT |
changed on BOTH sides | current kept; new version written beside it as <file>.harness-new |
NEW |
new in this harness version | installed |
ADOPT / CONFLICT-UNTRACKED |
file predates the manifest (legacy) | adopted into the manifest / .harness-new sibling |
DELETED-LOCALLY |
repo deleted it on purpose | respected, report-only (its manifest entry persists — even if later retired upstream) |
RETIRED |
dropped from the kit | file left in place; manifest entry dropped — deleting the file is the human's call |
If the report shows a LEGACY INSTALL banner, this repo predates manifests: the first --apply
adopts it (writes a fresh manifest); expect ADOPT/CONFLICT-UNTRACKED instead of the usual groups.
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 · 90 lines · 0 tokens per session scan A d6438c7e2787
sdlc-upgrade 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,324 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.
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.