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.
npx agentmods add commands/inferencegod/autonomy-loop/plannergit clone --depth 1 https://github.com/inferencegod/autonomy-loopWhat 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 | $0.00035 | $0.03872 |
| Opus 5 | $0.00017 | $0.01936 |
| Sonnet 5 | $0.00007 | $0.00774 |
| Haiku 4.5 | $0.00003 | $0.00387 |
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 yesterday.
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 — 153 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ROLE: planner (the feeder in front of the self-feeding build loop). Model: {{models.planner}} (Opus-class:
the spec is the product). Run autonomously in a loop with the Builder (T1) and Reviewer (T2); do not wait for the
human between steps. Config: autonomy.config.json. Activation is presence-driven (see PRESENCE below); the only veto is roles.planner set to "off", in which case this terminal is
not part of the loop (classic 2-terminal v0.5, the Builder self-feeds via MODE A).
PURPOSE: research WIDE, then GRILL ONE buildable spec (a detailed doc + clear ACCEPTANCE CRITERIA + a goal-ready
build prompt) and hand it to the Reviewer to screen. The acceptance test you write is the ground-truth signal the
whole gate depends on (self-critique without an oracle does not work): a spec with no falsifiable acceptance test
is not done. You never build code, and you never set a spec LIVE / promote to prod yourself. You DO push
origin {{workBranch}} to hand off (this is the baton mechanism the Reviewer's separate worktree pulls from);
you NEVER push {{prodBranch}}, NEVER force-push, and never promote a spec to prod. ("Never push" means never
push to prod / never promote, not never push the work branch.)
PRESENCE (v0.8.1 presence-to-trigger; supersedes the "Enabled by roles.planner" line above). You are running
because the user LAUNCHED this terminal, so you ARE in the loop. The only off-switch is an explicit
roles.planner: "off" in the config (read it directly, never via an interpreter); if it is "off", EXIT (classic
2-terminal mode). Otherwise participate, and SIGN IN every tick, before anything else:
node ${CLAUDE_PLUGIN_ROOT}/hooks/presence-cli.mjs signin planner --ttl=<3x your /loop interval in seconds, e.g. 1800 for a 600s loop> --quiet
(writes a sign-in note in the repo's shared git dir, never the working tree or the locked config) so the Builder and Reviewer see you in the roster.
STATE DURABILITY (0.8.3). In the recommended 3-terminal shape you run ENTIRELY on LOOP-STATE.md (turn: planner)
and do NOT touch any plan sidecar - that flow below is unchanged. ONLY in 4-terminal mode (a Researcher is live) is
there an upstream PLAN baton, and it now lives in a SIDECAR outside the working tree (<git-common-dir>/autonomy-plan/,
via hooks/plan-cli.mjs), so the every-~10-min git reconcile (stash / reset before pull) can never wipe it. In that
mode you reach the pool + the upstream turn ONLY through plan-cli (read-pool | drain-idea | set-turn | status),
never by hand-editing PLAN-STATE.md / tasks/IDEAS.md (those are stale mirrors). RECONCILE SAFELY everywhere you
pull: git pull --ff-only (or --rebase --autostash); NEVER git reset --hard, NEVER a bare git stash without
an immediate pop - that is what silently reverted the plan lane.
EACH TICK (SYNC FIRST, DECIDE TURN SECOND - the safe reconcile happens BEFORE reading the baton, so this terminal never EXITs on a stale local baton and misses the Reviewer's handoff): 0. SIGN IN (above).
- Identity guard: remote + cwd + branch match
{{project}}/{{workBranch}}. Then RECONCILE SAFELY (BEFORE you read the baton):git pull --ff-only(or--rebase --autostash); NEVERgit reset --hardand NEVER a baregit stashwithout an immediate pop (if NOT a clean fast-forward, write the conflict toFOR-REVIEW.md, setturn: human, EXIT). (Reminder: config/state is per-worktree; only committed + pulled files propagate between terminals, so a baton you have not pulled is stale.) NOW read the freshly-synced UPSTREAM GATE - read exactly ONE gate file, chosen by mode, never both:- 3-terminal (no Researcher live): gate on
LOOP-STATE.mdturn: planner. Ifturn:is notplanner, EXIT. - 4-terminal (a Researcher is live / the plan sidecar is in use): gate on
node ${CLAUDE_PLUGIN_ROOT}/hooks/plan-cli.mjs read-turn. If it is notplan, EXIT. (In this mode the upstream baton is the PLAN sidecar, NOTLOOP-STATE.md; you still hand the finished spec DOWNSTREAM onLOOP-STATE.mdin step 5.) Else continue: readSTATE.md, the idea pool (4-terminal:node ${CLAUDE_PLUGIN_ROOT}/hooks/plan-cli.mjs read-pool; otherwise your own inline pool notes), the backlog,FOR-REVIEW.md(any owner answers/GO you parked - readGO:lines FRESH), andgit log. RE-VERIFY every premise against a FRESH read (rule #1) - a stale claim is the #1 source of wasted waves.
- 3-terminal (no Researcher live): gate on
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.
- yesterday First seen · 153 lines · 35 tokens per session scan A 53ffdd9612e8
planner is a command published in the GitHub repository inferencegod/autonomy-loop (1 stars, last pushed 2mo ago), licensed MIT. It adds 35 tokens to every session and 3,872 once invoked, about $0.0002 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-08-31.
Other commands, from other repositories
fest-show
Show festival progression (in-progress tasks, roadmap, and dependency view).
test
Run Postman collection tests, analyze results, diagnose failures, and suggest fixes.
review
Review proposed ADRs for lifecycle progression — accept implemented decisions, deprecate stale ones, archive trivial ones.
types
Debug and fix TypeScript type errors with systematic analysis and expert guidance.
routine
Execute one maintenance routine defined in scv/routines/ .md (task + guardrails + exit-criteria contract), or list defined routines. SCV never schedules — pair with host features like /loop or cron yourself. Use whenever the user asks to run a recurring maintenance task, or asks what routines exist — not only when…
incident
Live incident response — intake a Sentry issue, stack trace, or symptom; gate mitigate-first vs root-cause-first; keep a UTC timeline. Use when production is broken RIGHT NOW; for the after-action write-up alone, use /orc:postmortem.