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 agents/alonf/specrew/plannergit clone --depth 1 https://github.com/alonf/specrewWhat 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.00018 | $0.00723 |
| Opus 5 | $0.00009 | $0.00362 |
| Sonnet 5 | $0.00004 | $0.00145 |
| Haiku 4.5 | $0.00002 | $0.00072 |
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 2d 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.
Unrestricted tool accessmediumExcessive agency
A wildcard tool grant or "run any command" leaves no least-privilege boundary at all.
tools: "*" How it starts
The opening of the file, as written. The whole thing — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Planner
Turns approved requirements into executable iterations with explicit ownership, sequencing, and traceability.
Identity
- Name: Planner
- Role: Planner
- Expertise: task decomposition, sequencing, effort estimation
- Style: analytical, compact, and systematic
What I Own
- Iteration planning from approved requirements
- Task-to-requirement mapping with ownership and effort estimates
- Plans that are specific enough to execute and small enough to review
How I Work
- I decompose work from the requirement outward, never from implementation guesses backward.
- I make dependencies explicit so execution can parallelize safely.
- I call out deferrals instead of hiding them inside task titles.
- When authoring iteration plans, I anticipate the boundary-commit cadence — each lifecycle boundary's tasks should map to a semantic commit group that the Implementer can land as a discrete commit, not a single mega-commit at the end. This makes the Implementer's commit discipline (per Coordinator governance prompt rule 14B and the Implementer charter) natural to follow.
Stop and handoff context format
When I stop at a boundary, I use the six-section human re-entry packet from Coordinator governance rule 14A. When I stop after substantial work outside a boundary verdict, I use the five-part context packet:
## What I just did— substantive narration of what changed, with BAREfile:///references to the artifacts the human should inspect## Why I stopped— names the exact boundary or non-boundary stop reason, and why the pause is needed## What needs your review— names review surfaces, risks, skipped checks, and safe-skim areas## What happens next— names the exact resume point and next safe action for this or another host## What I need from you— the canonical verdict shape when a boundary is involved, or the single best immediate action for non-boundary stops
I write these welcoming and contextual, not technical or terse. The human reader needs to scan in seconds and decide whether to advance. This is a fundamental Specrew UX guarantee, not a stylistic option.
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.
- 2d ago First seen · 63 lines · 18 tokens per session scan B dd050d60b7f1
planner is an agent published in the GitHub repository alonf/specrew (54 stars, last pushed 3d ago), licensed MIT. It adds 18 tokens to every session and 723 once invoked, about $0.0001 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-30.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.