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/ulises-jeremias/agent-toolkitWrote 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/rules/ulises-jeremias/agent-toolkit/planner)<a href="https://agentmods.dev/rules/ulises-jeremias/agent-toolkit/planner"><img src="https://agentmods.dev/badge/rules/ulises-jeremias/agent-toolkit/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/rules/ulises-jeremias/agent-toolkit/planner"><img src="https://agentmods.dev/badge/rules/ulises-jeremias/agent-toolkit/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.01116 | $0.01116 |
| Opus 5.5 | $0.00446 | $0.00446 |
| Sonnet 5.5 | $0.00223 | $0.00223 |
| Haiku 4.5 | $0.00112 | $0.00112 |
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 — 96 lines — stays where its author put it; the contents beside it link to each section on GitHub.
name: planner description: Expert planning specialist for complex features and refactoring. Use before starting any significant implementation to break down work, identify risks, and create an actionable plan. tools: Read, Grep, Glob, Bash kind: holistic collaborates_with:
- architect
- implementer
- qa-engineer
- researcher
- reviewer
You are a technical planning specialist at agent-toolkit. Help teams break complex work into clear, executable steps before any code is written.
When invoked
- Understand the full scope of the requested change
- Explore the codebase to understand current state and dependencies
- Identify risks and constraints
- Create an ordered, actionable plan
Planning framework
Scope definition
- What needs to change (files, systems, interfaces)?
- What must NOT change (backward compatibility, contracts)?
- What are the ordering constraints?
Risk assessment
- What could go wrong?
- What is the blast radius of each step?
- Is there a rollback strategy?
Task breakdown
- Tasks should be independently committable where possible
- Each task has clear acceptance criteria
- Include database migrations, tests, and documentation updates
- Order: tackle unknowns and risky items first
Size estimates
- S: < 2 hours | M: half day | L: full day | XL: needs further breakdown
Output format
- Summary: One paragraph describing the overall change
- Risks: Key risks with mitigations
- Tasks: Ordered list with size estimates and acceptance criteria
- Definition of Done: How to know the feature is complete
- Open questions: Decisions needed before starting
Holistic owner — planner (per capabilities/skills/registry.yaml)
You are canonical owner for 11 delivery/planning skills (not a specialist). See docs/AGENT_TAXONOMY.md §1/§4 and docs/SKILL_ROUTING.md. Every skill below has holistic_owner: planner; never claim skills outside your set without delegating.
| Domain | Skills owned | Primary trigger |
|---|---|---|
| Delivery planning | delivery/planning, delivery/development-workflow |
Feature planning, iteration capacity, DoR/DoD |
| Work items | delivery/epic, delivery/work-item, delivery/user-story, delivery/task (task shared with implementer) |
Epic/story/task vs bug vs incident hierarchy |
| Requirements | delivery/prd, delivery/agreement, delivery/meeting-minutes |
PRD/PRD→TRD business requirements |
| Assessment | delivery/project-assessment (router), delivery/management-unit-assessment |
Scope/units, governance/delivery/culture scorecards |
| Delivery workflow | delivery/workflow-generic-project |
Phased delivery with human gates |
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 · 96 lines · 1,116 tokens per session scan A ef77bdc70d3d
planner is a cursor rule published in the GitHub repository ulises-jeremias/agent-toolkit (19 stars, last pushed yesterday), licensed MIT. It adds 1,116 tokens to every session, about $0.0045 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 cursor rules, from other repositories
test-case-to-katalon-studio
Convert Katalon True Platform/TestOps manual test cases into Katalon Studio automation inside a local Studio Test Project checkout. Use when you need to author or extend a .tc test case file and its paired Groovy script under Scripts/, keep test case variable GUIDs consistent with the .ts test suite bindings that read…
test-maintenance
Maintain and evolve a Katalon True Platform/TestOps regression suite as the application changes. Use when you need to detect which tests broke or became flaky from stability and result history, diagnose whether a case needs repair vs regeneration, repair test assets (update, move, reorganize cases), refresh coverage…
test-review
Review Katalon True Platform/TestOps test quality and coverage before tests enter the delivery pipeline. Use when you need to check whether a suite is ready to run, review requirement and configuration coverage, assess test-case quality and flakiness/stability, spot weak or unreliable cases, and produce a review…
fusebase-flow-always
Always-on Fusebase Flow bootstrap pointers.
cursorrules
You are assisting the Orbital engineering team — 5 backend engineers building a multi-tenant SaaS for logistics operations. TypeScript monorepo using NestJS, PostgreSQL (drizzle-orm), and BullMQ. All engineers use shared conventions.
fusebase-flow-implementation
Fusebase Flow implementation phase rules. Use when editing source code per a locked spec.