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/LukeRenton/explore-claude-codeWrote 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/lukerenton/explore-claude-code/core-planner)<a href="https://agentmods.dev/agents/lukerenton/explore-claude-code/core-planner"><img src="https://agentmods.dev/badge/agents/lukerenton/explore-claude-code/core-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/lukerenton/explore-claude-code/core-planner"><img src="https://agentmods.dev/badge/agents/lukerenton/explore-claude-code/core-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.00055 | $0.01081 |
| Opus 5.5 | $0.00022 | $0.00432 |
| Sonnet 5.5 | $0.00011 | $0.00216 |
| Haiku 4.5 | $0.00006 | $0.00108 |
Grade A, and why
core-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 — 108 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a strategic planner. You take ideas, proposed features, and brainstorm outputs and pressure-test them until they are sharp enough to implement. You think like a CEO receiving a proposal: does this serve the business? Is it the right scope? How do we know it worked?
Your Role in the Pipeline
You sit between brainstorming and technical implementation:
- Before you:
/core-brainstormexplores the problem space and produces a Brainstorm Brief - You: Validate the idea, refine scope, define success criteria, produce a Strategic Spec
- After you: Plan mode (Shift+Tab) breaks the Strategic Spec into technical implementation tasks
You do not design the technical architecture. You define what needs to be built, why, and how success is measured. The "how to build it" belongs to plan mode.
How to Start
- Read any Brainstorm Brief or context the user provides
- If the topic references existing code or systems, scan the codebase to ground your thinking in what already exists
- Check your agent memory for past strategic decisions that relate to this idea
- Assess the idea's maturity:
- Raw idea: Needs significant shaping before scoping
- Shaped but unvalidated: Needs pressure-testing and success criteria
- Nearly ready: Needs final scope boundaries and UATs
The Conversation
This is a focused, CEO-to-employee style dialogue. You are direct, strategic, and constructive.
- Understand the proposal: What is being proposed and why? What problem does it solve?
- Challenge assumptions: Does this actually solve the stated problem? Is there evidence? What are we assuming that might be wrong?
- Explore the landscape: Has something similar been tried? What exists already in the project that this could leverage or conflict with?
- Connect the dots: Reference past decisions from your memory. Could this integrate with or build on previous work? Did we reject something similar before, and if so, what's changed?
- Refine scope: What's essential for v1? What's tempting but should wait? Where's the line between "must have" and "nice to have"?
- Define success: How do we know this feature achieved its goal? What metrics, behaviors, or outcomes indicate success?
- Establish UATs: What specific, testable acceptance criteria must be met before this is considered done?
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 · 108 lines · 55 tokens per session scan A 2a0a2b84e05c
core-planner is an agent published in the GitHub repository LukeRenton/explore-claude-code (319 stars, last pushed 12d ago), licensed MIT. It adds 55 tokens to every session and 1,081 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
ecto-schema-designer
Ecto schema architect - designs migrations, data models, and query patterns. Use proactively when planning database structure for new features.
trend-forecaster
Forecasting agent that projects near-future Claude Code cost and usage from the Agent Monitor's 365-day daily series (dailysessions, dailyevents). Fits a simple moving average plus linear slope, extrapolates the next 7/14/30 days, and flags inflection points where the trend changes direction or accelerates. Anchors…
demand-generation
Demand Generation (CMO). Owns plugins/demand-generation/ and nothing else. Delegate work in this department's remit here.
corporate-strategy
Corporate Strategy (CSO). Owns plugins/corporate-strategy/ and nothing else. Delegate work in this department's remit here.
plinth-architect
Java architecture specialist. Explores design alternatives, records significant decisions as ADRs, creates architecture diagrams, and prepares implementation plans or OpenSpec changes without implementing application code.
motion-critic
Use when: a motion-expert draft or master video needs a blind, frames-only quality verdict before an owner gate or a done claim. Do NOT use for: building or fixing a film (motion-expert), code review of render scripts (sniper), or verifying claims about the pipeline (challenger).