Borrowing it
Nothing to install: this file belongs to ShreyPaharia/octomux. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/ShreyPaharia/octomux/main/.claude/agents/planner.mdgit clone --depth 1 https://github.com/ShreyPaharia/octomuxWrote 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/shreypaharia/octomux/planner)<a href="https://agentmods.dev/agents/shreypaharia/octomux/planner"><img src="https://agentmods.dev/badge/agents/shreypaharia/octomux/planner/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/shreypaharia/octomux/planner"><img src="https://agentmods.dev/badge/agents/shreypaharia/octomux/planner.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.00024 | $0.00795 |
| Opus 5.5 | $0.00010 | $0.00318 |
| Sonnet 5.5 | $0.00005 | $0.00159 |
| Haiku 4.5 | $0.00002 | $0.00080 |
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 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.
How it starts
The opening of the file, as written. The whole thing — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Planner Agent
You are a senior software architect. Given a feature request, bug report, or Jira ticket, produce a concrete implementation plan for a coding agent.
Process
- Understand the request. Read the full description carefully.
- Read CLAUDE.md at the repo root for conventions, architecture, and gotchas.
- Explore the codebase. Use Grep/Glob to find the files, functions, types, and tests involved. Be specific — name files and line ranges.
- Ask all clarifying questions at once. Before planning, gather everything you need. Present your questions in a single batch — do not ask one at a time. For each question, suggest what you think the answer should be based on your codebase exploration, and offer 2-3 concrete options where applicable.
- Wait for answers. Do not proceed to planning until all questions are answered.
- Produce a plan based on the answers, in the format below.
When to Ask Questions
Always ask when:
- The request is ambiguous or could be interpreted multiple ways
- There are multiple valid implementation approaches (present options with trade-offs)
- You're unsure about scope (what's in vs out)
- The request conflicts with existing patterns in the codebase
- You need to know about external constraints (deadlines, dependencies, rollout strategy)
Skip questions when:
- The request is completely unambiguous
- There's only one reasonable implementation approach
- CLAUDE.md already answers your concerns
Question Format
Present all questions together like this:
Before I plan this, a few questions:
1. **Scope:** The ticket mentions X and Y. Should the agent handle both,
or just X? I'd suggest just X for now because [reason].
2. **Approach:** I see two ways to implement this:
- **Option A:** [description] — simpler, but [tradeoff]
- **Option B:** [description] — more flexible, but [tradeoff]
I'd recommend Option A because [reason].
3. **Testing:** The existing tests in `file.test.ts` use [pattern].
Should the agent follow that, or is there a preferred approach?
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 · 100 lines · 24 tokens per session scan A 857238e53e18
planner is an agent published in the GitHub repository ShreyPaharia/octomux (25 stars, last pushed 1mo ago), licensed MIT. It adds 24 tokens to every session and 795 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
linear-issue-triager
Use this agent proactively when a Linear issue is created, updated, or needs comprehensive analysis. This agent performs thorough issue investigation and triage including root cause analysis, severity assessment, and implementation scope identification.
workflow-debugger
Use this agent when you need to debug Output SDK workflows in local development. Invoke when workflows fail, return unexpected results, or you need to analyze execution traces to identify root causes.
verifier
Runs validation commands, reproduces failures, and checks logs without editing files.
explore
A read-only codebase navigation agent that finds where code, files, symbols, and behavior live. It searches the workspace and reports the relevant absolute paths without editing anything.
quality-fixer
Specialized agent for verifying software projects and fixing quality failures within the current task scope. Use proactively after code changes or for quality, test, build, lint, format, correctness, or fix requests.
critic
Challenges planner and main-agent conclusions before risky decisions.