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/programme-bundle-review)<a href="https://agentmods.dev/commands/stevegjones/ai-first-sdlc-practices/programme-bundle-review"><img src="https://agentmods.dev/badge/commands/stevegjones/ai-first-sdlc-practices/programme-bundle-review.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.1 | $0.00000 | $0.01710 |
| Opus 5 | $0.00000 | $0.00855 |
| Sonnet 5 | $0.00000 | $0.00342 |
| Haiku 4.5 | $0.00000 | $0.00171 |
Grade A, and why
programme-bundle-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 7d 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 — 129 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Programme Bundle Review
Your Role
You are a senior solution architect reviewing the Programme bundle (plugins/sdlc-programme/) — the Method 1 phase-gate substrate from EPIC #178 Phase D. Phase E (Assured bundle) layers on top of this; getting Programme right matters.
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.
What you're reviewing
Primary input: plugins/sdlc-programme/ (the entire bundle).
Walk these files specifically:
plugins/sdlc-programme/manifest.yaml— bundle manifestplugins/sdlc-programme/CONSTITUTION.md— Programme constitution (Articles 12-14)plugins/sdlc-programme/templates/{requirements-spec,design-spec,test-spec}.md— phase artefact templatesplugins/sdlc-programme/scripts/programme/spec_parser.py— ID extractionplugins/sdlc-programme/scripts/programme/gates.py— 4 phase-gate validatorsplugins/sdlc-programme/scripts/programme/traceability.py— REQ↔DES↔TEST matrixplugins/sdlc-programme/skills/{commission-programme,phase-init,phase-gate,phase-review,traceability-export}/SKILL.md— 5 skillsplugins/sdlc-programme/README.md— bundle overview
Required context
Read these adjacent documents before the review:
docs/architecture/option-bundle-contract.md— bundle contract (Phase C deliverable). The Programme bundle MUST conform to this.docs/feature-proposals/186-phase-d-programme-bundle-substrate.md— Phase D scope specdocs/superpowers/specs/2026-04-26-programme-assured-bundles-design.md§3 — Method 1 designresearch/sdlc-bundles/METHODS.md§3 — Method 1 design summarytests/fixtures/programme/feature-sample/— minimal feature fixture used by gate teststests/test_programme_*.py— 27 tests covering the bundle- The Phase B containerised review at
research/sdlc-bundles/dogfood-workflows/architect-review-spike-output.mdand Phase C task 10 review atresearch/sdlc-bundles/dogfood-workflows/bundle-contract-review-output.mdfor review-style precedents
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.
- 7d ago First seen · 129 lines · 0 tokens per session scan A 934d714bea63
programme-bundle-review is a command published in the GitHub repository SteveGJones/ai-first-sdlc-practices (41 stars, last pushed 28d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,710 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.
review-sdk-app
Review and validate a Claude Agent SDK application against best practices.
repo-audit
Audit a codebase (local or remote GitHub/GitLab) against architecture principles and requirements, surfacing drift, risk, and missing decisions.
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.