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.
git clone --depth 1 https://github.com/lantisprime/claude-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/lantisprime/claude-sdlc/build)<a href="https://agentmods.dev/commands/lantisprime/claude-sdlc/build"><img src="https://agentmods.dev/badge/commands/lantisprime/claude-sdlc/build/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/lantisprime/claude-sdlc/build"><img src="https://agentmods.dev/badge/commands/lantisprime/claude-sdlc/build.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00019 | $0.00234 |
| Opus 5.5 | $0.00008 | $0.00094 |
| Sonnet 5.5 | $0.00004 | $0.00047 |
| Haiku 4.5 | $0.00002 | $0.00023 |
Grade A, and why
build 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 1mo 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.
What it actually says
Invoke the build skill. Prerequisite: .claude/sdlc/gates/design-<task-slug>.md.
The skill coordinates with surgical-edit, minimal-code, and security-review. Hooks enforce:
plan-gate— no Edit/Write without a planwork-item-validation— builds reference a REQ ID / ticket / signed CRdiff-scope-check— only plan-listed files are modifiedadjacent-function-detector— only plan-listed functions are modifiedmodified-code-test-gate— unit tests added only for functions actually modifiedformat-on-write— formatter runs on every changed filesecret-scan— blocks secrets committed to the diff
Produces: code + unit tests + deployment/pipeline deltas.
On completion, invoke the gate-signoff skill to capture the human sign-off via chat and write .claude/sdlc/gates/build-<task-slug>.md.
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.
- 1mo ago First seen · 20 lines · 19 tokens per session scan A 989a2bb43b42
build is a command published in the GitHub repository lantisprime/claude-sdlc (3 stars, last pushed 5mo ago), licensed MIT. It adds 19 tokens to every session and 234 once invoked, about $0.0001 per session on Opus 5.5. 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
poc
Before building on an unproven idea, get a timeboxed yes/no answer — start a hypothesis-driven POC that skips 80% of the production pipeline and forces ship/pivot/kill at expiry, then promote a shipped POC through the audits it skipped.
ownership
When you need to know who owns a path and who answers for it — the service ownership matrix (team, lead, on-call, SLA) auto-detected from git with CODEOWNERS generated, plus on-call rotations, shift handoffs and escalation paths.
rfc
RFC process for cross-team decisions. Create, track, and close RFCs. Accepted RFCs auto-create ADRs.
exception
Signed gate-exception registry — replace ad-hoc --admin / --no-verify bypasses with an auditable, signed, expiring record (who · why · gate · scope · expiry). Create / list / check exceptions.
handoff
You are generating a self-contained briefing optimized for a successor — someone who needs to continue this sprint, not a stakeholder making a decision. Read CLAUDE.md, claims.json, and compilation.json.
merge
You are merging claims from another sprint into the current one. This is for when two teams researched the same problem independently and need to combine their findings.