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/SteveGJones/ai-first-sdlc-practicesWrote 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/stevegjones/ai-first-sdlc-practices/bundle-contract-review)<a href="https://agentmods.dev/commands/stevegjones/ai-first-sdlc-practices/bundle-contract-review"><img src="https://agentmods.dev/badge/commands/stevegjones/ai-first-sdlc-practices/bundle-contract-review/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/stevegjones/ai-first-sdlc-practices/bundle-contract-review"><img src="https://agentmods.dev/badge/commands/stevegjones/ai-first-sdlc-practices/bundle-contract-review.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.00000 | $0.01490 |
| Opus 5 | $0.00000 | $0.00745 |
| Sonnet 5 | $0.00000 | $0.00298 |
| Haiku 4.5 | $0.00000 | $0.00149 |
Grade A, and why
bundle-contract-review 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 10d 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 — 120 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Bundle Contract Review
Your Role
You are a senior solution architect reviewing the bundle contract specification for the AI-First SDLC framework. The contract is docs/architecture/option-bundle-contract.md — the authoritative spec for what an option bundle contains, how it's packaged, and what schema fields it must support.
You operate in a fresh container with SDLC plugins installed. Use the sdlc-team-common:solution-architect agent (via the Agent tool with subagent_type="sdlc-team-common:solution-architect") for the architectural review — this command file briefs the agent and captures their output as your structured review.
The contract is load-bearing: Phase D (#103, Programme bundle) and Phase E (#104, Assured bundle) will both build bundles against this contract. Schema mistakes here propagate. Your review must be rigorous.
What you're reviewing
Primary input: docs/architecture/option-bundle-contract.md (in the worktree).
Read the WHOLE document before reviewing. It has these sections:
- Title + metadata (Version, Status, Authoritative for)
- "What a bundle is" — defines what a bundle contains
- "File layout" — directory tree
- "Manifest schema" — required + optional fields table
- "Reserved Phase E fields" — 5 capability flags
- "Versioning rules" — semver semantics
- "Reserved schema for
.sdlc/team-config.json" — required + reserved fields - "Validator configuration" — YAML example with bundle-defined identifier semantics
- "Backward compatibility" — uncommissioned project default
- "What Phase C does NOT cover" — out-of-scope
Required context
Read these adjacent documents before the review:
docs/superpowers/specs/2026-04-26-programme-assured-bundles-design.md— design spec the contract servesresearch/sdlc-bundles/METHODS.md— Method 1 / Method 2 design that drives bundle requirementsresearch/sdlc-bundles/decomposition-spike.md— Phase B output with 4 schema gaps the contract reserveslibrary/regulatory-traceability-baseline.md— regulatory rigour the Assured bundle must supportlibrary/decomposition-ddd-bazel.md— decomposition primitive the Assured bundle must accommodate
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.
- 10d ago First seen · 120 lines · 0 tokens per session scan A 1614785bd5a4
bundle-contract-review is a command published in the GitHub repository SteveGJones/ai-first-sdlc-practices (41 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,490 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-30.
Other commands, from other repositories
sdd-init
Initialize SDD context — detects project stack and bootstraps persistence backend.
review-branch
Review the current branch's diff against base by dispatching atomic-reviewer. No orchestration loop, no spec required — pre-flight before /commit pr or /commit merge.
init
Install the formatters this repository needs, with every command visible before it runs.
repo-audit
Audit a codebase (local or remote GitHub/GitLab) against architecture principles and requirements, surfacing drift, risk, and missing decisions.
argos
A command for checking whether an implementation matches its design deliverables. Its Korean description compares the work to the design as part of a completion inspection.
security-review
AI-powered security review of the current git diff (or specified paths). Dispatches the security-reviewer agent and prints findings grouped by severity.