Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add SteveGJones/ai-first-sdlc-practices/plugin install sdlc-model-councilWrote 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/backends)<a href="https://agentmods.dev/commands/stevegjones/ai-first-sdlc-practices/backends"><img src="https://agentmods.dev/badge/commands/stevegjones/ai-first-sdlc-practices/backends/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/backends"><img src="https://agentmods.dev/badge/commands/stevegjones/ai-first-sdlc-practices/backends.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.00021 | $0.00509 |
| Opus 5 | $0.00010 | $0.00254 |
| Sonnet 5 | $0.00004 | $0.00102 |
| Haiku 4.5 | $0.00002 | $0.00051 |
Grade A, and why
backends 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.
What it actually says
Report the current backend registry for sdlc-model-council.
Do this:
- Run:
${CLAUDE_PLUGIN_ROOT}/scripts/extdel.sh list-backends $ARGUMENTS(pass through--probe-authif the caller asked for a live auth check; otherwise run it with no arguments — this is a pure read-only report, no handle is created and no external-provider tokens are spent unless--probe-authis explicitly requested). - Show the table as-is: id, vendor, installed, auth, kind, postures(fidelity), sibling.
- For any backend reported
installed: no, add a one-line install hint for the underlying CLI (e.g.codex: see OpenAI's Codex CLI install docs;agy: see Antigravity's install docs) — this plugin only wraps an already-installed binary, it does not install one. - For any row whose
siblingcolumn isinstalled, mention the matching sibling plugin's own slash commands as an alternative worth considering for that backend (codex→/codex:review,/codex:adversarial-review,/codex:rescue,/codex:transfer,/codex:status,/codex:result,/codex:cancel, installable via/plugin install codex@openai-codex;agy→/antigravity:delegate,/antigravity:review,/antigravity:research,/antigravity:cloud-run-debug,/antigravity:status,/antigravity:result,/antigravity:cancel, installable via/plugin install antigravity@antigravity-for-claude-code) — point to thecouncil-policyskill's routing table for when to prefer the sibling plugin over/…:delegate. - For any row whose
siblingcolumn isabsent, still name the sibling plugin and its/plugin installcommand as an FYI, in case the caller wants the vendor-native depth it offers alongside this plugin's cross-vendor uniformity.
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 · 38 lines · 21 tokens per session scan A 4fff34a27229
backends is a command published in the GitHub repository SteveGJones/ai-first-sdlc-practices (41 stars, last pushed 1mo ago), licensed MIT. It adds 21 tokens to every session and 509 once invoked, about $0.0001 per session on Opus 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-09-03.
Other commands, from other repositories
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.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.