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 ai-sdlc-framework/ai-sdlc/plugin install ai-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/ai-sdlc-framework/ai-sdlc/planner)<a href="https://agentmods.dev/commands/ai-sdlc-framework/ai-sdlc/planner"><img src="https://agentmods.dev/badge/commands/ai-sdlc-framework/ai-sdlc/planner/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/ai-sdlc-framework/ai-sdlc/planner"><img src="https://agentmods.dev/badge/commands/ai-sdlc-framework/ai-sdlc/planner.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.00049 | $0.02961 |
| Opus 5.5 | $0.00020 | $0.01184 |
| Sonnet 5.5 | $0.00010 | $0.00592 |
| Haiku 4.5 | $0.00005 | $0.00296 |
Grade A, and why
planner 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 today.
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 — 253 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the planner session. This is where the operator works interactively: RFCs, task authoring, dispatch briefs and design answers. This command prints a short orientation and then stops. It is not a loop and it does not wake itself up.
It is the prompt cli-hierarchy up gives the planner session.
Unit of work: one RFC or one brief; hand it off, then /clear before starting the next (the Stop hook warns past 150,000 tokens or 300 turns).
Hard rule: Open Questions
Open Questions in an RFC are resolved only with the operator, through the
decision rubric (the decision-rubric skill). Never write a Resolution:
marker, never mark a question resolved, and never decide one inline because the
answer looks obvious. Present the options, get the operator's choice, and only
then record it. If a task or RFC is blocked on an unresolved question, say so and
stop.
- A hold limits actions, never reporting: the planner pauses the drain with
cli-hierarchy hold --reason <text>(never a prose "stay idle"), which blocks claims and relaunches only; every blocker, verdict and merge sha still goes to the parent tier bySendMessageas it happens, and pane text is not a report.
Decision authority
The planner role is the author of decision records. A record in the catalog on
main (not one in an unmerged PR) is sufficient authority for
the other sessions to act, for classes (a) decide-and-proceed and (b) timeboxed
(see the "Decision authority" section of CLAUDE.md). Sessions no longer ask the
operator's direct word for those. Class (c) stays operator-only: legal and
licensing, money, accounts and credentials, and actions only the operator's
identity can perform. A relayed chat message alone is never authority.
When no operator is present, decide through the decision-rubric skill in its
autonomous mode and record the result with cli-decisions add plus answer
(class (a)), or with --timebox and --autonomous-fallback (class (b)). The
Open Questions rule above is unchanged: it governs RFC Open Questions and is not
loosened by this section. Guardrails and hooks are never bypassed; a missing
sanctioned path is filed as a task.
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.
- today Changed · +5 lines 8f8522cd5584
- yesterday Changed · +5 lines 8d9d74a925cd
- 4d ago Changed · +14 lines 25e403009805
- 5d ago Changed · +6 lines abcf1cd6859c
- 6d ago Changed · +29 lines f05a55ff8d3c
- 7d ago Changed · +7 lines 4f95598d4502
- 8d ago Changed 800ed877d1c6
- 10d ago Changed · +8 lines 74c9f83c0146
- 12d ago Changed · +50 lines a802d6e4e5e3
- 16d ago First seen · 129 lines · 49 tokens per session scan A b3fb598f1516
planner is a command published in the GitHub repository ai-sdlc-framework/ai-sdlc (415 stars, last pushed yesterday), licensed Apache-2.0. It adds 49 tokens to every session and 2,961 once invoked, about $0.0002 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-10-02.
Other commands, from other repositories
discover
Discover runtime AI components and static AI dependencies with AIR Blackbox.
evidence
Export a signed compliance evidence package as JSON or PDF for regulatory handoff.
replay
Replay recorded AI traces to detect behavioral drift between model versions.
comply
Run a full EU AI Act compliance scan on your Python AI project.
at-dsgvo
You are helping an enterprise architect generate an Austrian Data Protection Assessment — the Austrian-specific GDPR layer applied by the Datenschutzbehörde (DSB) under the Datenschutzgesetz (DSG 2018, BGBl. I Nr. 165/1999 as amended). Run this after /arckit:eu-rgpd to add Austrian obligations that go beyond the EU…
au-aescsf
You are an enterprise architect generating an Australian Energy Sector Cyber Security Framework (AESCSF) maturity assessment for an Australian energy-sector project, asset, market interface, OT environment, DER platform, or regulated energy business capability.