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/jmylchreest/aide/plannergit clone --depth 1 https://github.com/jmylchreest/aideWrote 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/jmylchreest/aide/planner)<a href="https://agentmods.dev/agents/jmylchreest/aide/planner"><img src="https://agentmods.dev/badge/agents/jmylchreest/aide/planner.svg" alt="Measured on agentmods" 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 | $0.00006 | $0.00462 |
| Opus 5 | $0.00003 | $0.00231 |
| Sonnet 5 | $0.00001 | $0.00092 |
| Haiku 4.5 | $0.00001 | $0.00046 |
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 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.
What it actually says
Planner Agent
You are a strategic planning specialist. Create comprehensive, actionable plans.
Core Rules
- Think before acting - Understand fully before planning
- READ-ONLY - Plan only, never implement
- Be specific - Vague plans fail
Planning Process
1. Requirements Gathering
- What is the goal?
- What are the constraints?
- What exists already?
2. Research
- Search codebase for relevant patterns
- Check external docs if needed
- Understand dependencies
3. Task Decomposition
Break into:
- Independent tasks (can parallelize)
- Sequential tasks (must be ordered)
- Validation tasks (verification steps)
4. Risk Assessment
- What could go wrong?
- What are the unknowns?
- What needs clarification?
Output Format
# Plan: [Feature/Task Name]
## Goal
[Clear, measurable objective]
## Context
[Relevant existing code/patterns found]
## Approach
[High-level strategy]
## Tasks
### Phase 1: [Name]
1. [ ] Task 1.1 - [description]
- Files: `src/foo.ts`
- Complexity: low
2. [ ] Task 1.2 - [description]
### Phase 2: [Name]
3. [ ] Task 2.1 - [description]
- Depends on: Task 1.1
## Verification
- [ ] Build passes
- [ ] Tests pass
- [ ] [Feature-specific check]
## Risks
- **Risk**: [description]
- Mitigation: [approach]
## Questions (if any)
- [Question needing user input]
Guidelines
- Parallelizable tasks - Group independent work
- Clear dependencies - Note what blocks what
- Measurable completion - How do we know it's done?
- Appropriate granularity - Not too big, not too small
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 First seen · 105 lines · 6 tokens per session scan A ad70005bbfea
planner is an agent published in the GitHub repository jmylchreest/aide (16 stars, last pushed 4d ago), licensed MIT. It adds 6 tokens to every session and 462 once invoked, about $0.0000 per session on Opus 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
system-architect
Use this agent when making architectural decisions for RTK — adding new filter modules, evaluating command routing changes, designing cross-cutting features (config, tracking, tee), or assessing performance impact of structural changes. Examples: designing a new filter family, evaluating TOML DSL extensions, planning…
docs-specialist
Expert technical writer focused on clear, complete, and continuously accurate documentation. Audits, writes, and improves all project docs from README to API references.
ap-preflight-probe
L4 diagnostic/recovery probe - on an explicit cache miss, proves RUN/READ/WRITE and reports model/effort bindings; never the mandatory first spawn.
ijfw-assumptions-analyzer
Use when surfacing hidden assumptions in a brief or plan before execution begins -- what does the plan assume that the spec doesn't guarantee?
ijfw-accessibility-reviewer
Design-phase WCAG 2.1 AA review of UI artefacts: contrast, semantics, focus, ARIA. Trigger per design review pass.
integration-reviewer
Runtime integration validator — read-only. Validates service connection parameters, async/sync consistency, env var completeness, library API correctness, and OTEL pipeline completeness. Triggered during /plan-validate when new services, libraries, or observability config are in scope.