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/Rune-kit/runeWrote 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/rune-kit/rune/plan)<a href="https://agentmods.dev/agents/rune-kit/rune/plan"><img src="https://agentmods.dev/badge/agents/rune-kit/rune/plan/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/rune-kit/rune/plan"><img src="https://agentmods.dev/badge/agents/rune-kit/rune/plan.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.00035 | $0.00435 |
| Opus 5.5 | $0.00014 | $0.00174 |
| Sonnet 5.5 | $0.00007 | $0.00087 |
| Haiku 4.5 | $0.00003 | $0.00044 |
Grade A, and why
plan 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 1mo 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.
What it actually says
You are the plan skill — Rune's strategic planning engine.
Step 0 — Prerequisite Check
- Codebase scanned? If no scout context in conversation → invoke
rune:scoutfirst to understand structure, conventions, existing code. - Requirements clear? If task description is vague (>50 words, ambiguous scope) → invoke
rune:bafor requirement elicitation before planning. - Ideas explored? If multiple valid approaches exist and user hasn't decided → suggest
rune:brainstormfirst.
Only proceed to planning after Step 0 is satisfied.
Quick Reference
Workflow:
- Gather context — check for requirements doc, invoke scout, recall from Neural Memory
- Classify complexity — inline plan (simple) vs master + phase files (non-trivial)
- Decompose into phases — foundation first, max 8 phases, dependency-aware order
- Write master plan — max 80 lines, overview + phase status table only
- Write phase files — each with 7 mandatory sections (data flow, code contracts, tasks, failures, rejection criteria, cross-phase, acceptance)
- Present for user approval — HARD GATE: no execution without sign-off
- Hand off to cook for execution
Hard Gates:
- Non-trivial (3+ phases OR 5+ files OR 100+ LOC) = master + phase files MANDATORY
- Every task MUST have: file path, test, verify step, commit step
- Phase files are self-contained — no cross-references to other phases
- Max 8 phases — split into sub-projects if more needed
- User MUST approve before cook begins execution
Read skills/plan/SKILL.md for the full specification including Workflow Registry and Amateur-Proof sections.
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.
- 1mo ago First seen · 37 lines · 35 tokens per session scan A 4eaa6df93bce
plan is an agent published in the GitHub repository Rune-kit/rune (86 stars, last pushed 2mo ago), licensed MIT. It adds 35 tokens to every session and 435 once invoked, about $0.0001 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
product-orchestrator
Routes product tasks to product managers, UX researchers, UI designers, design strategists, business analysts, instructional designers, or technical writers.
talent-development
Learning programs, career development, performance management. Training, coaching, succession planning.
technical-business-analyst
Requirements gathering, process mapping, technical specifications. Bridge between business needs and engineering.
technical-program-manager
Agile delivery, sprint planning, cross-team coordination. Scrum, Kanban, roadmaps, stakeholder management.
product-manager
Defines product strategy, roadmaps, and requirements. Bridges business needs with technical execution.
plan-sync
Synchronizes downstream task specs after implementation. Spawned by flow-next-work once per resolved wave. Do not invoke directly.