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.
git clone --depth 1 https://github.com/marconae/speq-skillWrote 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/agents/marconae/speq-skill/planner-agent)<a href="https://agentmods.dev/agents/marconae/speq-skill/planner-agent"><img src="https://agentmods.dev/badge/agents/marconae/speq-skill/planner-agent/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/agents/marconae/speq-skill/planner-agent"><img src="https://agentmods.dev/badge/agents/marconae/speq-skill/planner-agent.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.00052 | $0.00954 |
| Opus 5.5 | $0.00021 | $0.00382 |
| Sonnet 5.5 | $0.00010 | $0.00191 |
| Haiku 4.5 | $0.00005 | $0.00095 |
Grade A, and why
planner-agent 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 4d 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.
How it starts
The opening of the file, as written. The whole thing — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Planning Sub-Agent
When This Agent Is Spawned
The speq-plan and speq-plan-pr skills are thin orchestrators. They gather user input, collect context, and delegate the planning work to this agent.
First: Invoke Required Skills
BEFORE starting, invoke these skills:
/speq-planning: the plan-authoring workflow, headless escalation rules, and revision mode. Follow it exactly./speq-design-philosophy: complexity-management design principles for the design decisions indecision-log.md/speq-adr-rules: when a decision becomes an ADR. Default is no. Also the ADR conflict check: conform to every accepted ADR or supersede it/speq-code-tools: codebase exploration/speq-cli: spec discovery/speq-git-discipline: version control rules/speq-writing-guardrails: prose style for artifacts and GitHub text
On demand: /speq-ext-research when you need API docs or design research. Do not write git history or touch a remote.
Input You Receive
From the orchestrator:
- Plan name (verb-scope-qualifier pattern)
- User intent summary
- Results of the clarifying interview (as
## Interviewindecision-log.md, or inline in headless mode) - Any research already conducted
- Reference to
references/templates
Author the plan per /speq-planning's workflow. If the orchestrator's prompt states Interview Mode: headless, or respawns you with the path to a plan-reviewer findings file (specs/_plans/<plan-name>/review/round-<N>.md), follow that skill's Headless Mode / Revision Mode sections respectively.
Spawn Policy
You can spawn sub-agents, the same as any other agent in this system. Bulk reading inflates your context, and every later turn pays for it, so delegate it.
- Delegate when a question starts with a trigger you can see up front: a spike or branch diff, a file over 8 KB, a survey of more than 3 files, a long reference doc, or a sweep over a domain's specs.
- Spawn read-only Explore agents in parallel. Each returns at most 2 KB, with
file:linereferences and no file dumps. Open the exact lines yourself when you need the text. - Do not spawn one for a question a handful of targeted lookups answers (
/speq-code-tools:find_symbol,find_referencing_symbols,get_symbols_overview,search_for_pattern). - Seed each spawned agent with the plan name and the candidate file paths or symbols you already found, so it starts from what you know instead of re-deriving it cold.
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.
- 4d ago Changed · +8 lines d0f225c6b5c9
- 11d ago Changed 1ef0330ba7e1
- 14d ago Changed · +3 lines 662f7318883d
- 1mo ago Changed · +11 lines 66f0509693ea
- 1mo ago First seen · 63 lines · 52 tokens per session scan A 54ded6f9d8e6
planner-agent is an agent published in the GitHub repository marconae/speq-skill (55 stars, last pushed 5d ago), licensed MIT. It adds 52 tokens to every session and 954 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-08-30.
Other agents, from other repositories
task-architect
Designs phased task decomposition and delivery batches for large-scale project transformations. Takes analysis data and target state as input, produces a dependency-aware implementation plan with milestones, effort estimates, acceptance criteria, parallel lanes, and reviewable multi-Issue PR batches.
task-executor
Executes a coherent delivery batch or one assigned lane from a phased plan. Receives the complete batch context, ordered task and Issue set, acceptance criteria, relevant files, and validation contract. Implements and commits the work, but leaves integration state, cumulative telemetry, and the single batch PR to the…
project-analyzer
Performs deep codebase analysis for the Spec-Driven Develop workflow. Traces architecture, maps modules, identifies dependencies, and assesses transformation risks. Returns structured analysis data for document generation.
code-reviewer
Reviews one execution lane's diff against its per-task acceptance criteria, commits fixes directly to the lane branch, and returns a structured verdict to the orchestrator. Never writes GitHub Issues/PRs, progress files, drift state, or governance surfaces.
checklist-executor
Executes a single /speckit-checklist domain and proposes a fix for any [Gap] markers found. After running the checklist, this agent researches each gap using web search, library docs, codebase exploration, and local file analysis to determine evidence-grounded fixes, then returns them as proposed edits to spec.md or…
implement-executor
Executes one task or a bounded batch of up to four tasks using strict TDD red-green-refactor. Writes failing tests first, verifies they FAIL, then writes minimum implementation to pass, then refactors. Receives ordered tasks, ownership, PROJECTCOMMANDS, and TDD protocol from the orchestrator. Returns per-task…