planner

A planner that breaks a feature into small deliverable tasks, maps their dependencies, and defines how each task will be accepted.

In plain words
What is it for?
Use it to decompose features into atomic tasks, arrange tasks that depend on one another, write acceptance criteria, and run a pre-mortem.
Why use it?
It turns broad feature requests into an ordered plan and considers likely ways the work could fail before implementation starts.

Agent

Install

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.

agentmods
npx agentmods add agents/zebbern/termstack/planner
Clone the repo
git clone --depth 1 https://github.com/zebbern/termstack
Per session 32 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 5,234 The whole file, excluding the scripts and references it only reads on demand.
Security scan B 1 finding. Scan, not verified.
Origin unknown No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00032 $0.05234
Opus 5 $0.00016 $0.02617
Sonnet 5 $0.00006 $0.01047
Haiku 4.5 $0.00003 $0.00523

Measured yesterday against content hash 6cb6caff8ca1, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade B, and why

planner scanned grade B with 1 finding 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.

Unrestricted tool accessmediumExcessive agency

A wildcard tool grant or "run any command" leaves no least-privilege boundary at all.

3. **Scope boundary**: You produce a plan. You do NOT implement the plan, verify it, or execute any code. If you find yourself writing implementation code, STOP — that is the Executor's job.
.github/agents/planner.agent.md · 465 lines

The source is not reproduced here

No licence file

A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.

Read it on GitHub

Changes

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.

  1. yesterday First seen · 465 lines · 32 tokens per session scan B 6cb6caff8ca1

Subscribe to this mod's changes

planner is an agent published in the GitHub repository zebbern/termstack (5 stars, last pushed 4mo ago), with no licence file. It adds 32 tokens to every session and 5,234 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it B with 1 finding (unrestricted tool access). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.