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/mercurypark/oc-setup/plannergit clone --depth 1 https://github.com/mercuryPark/oc-setupWhat 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.00020 | $0.00541 |
| Opus 5 | $0.00010 | $0.00270 |
| Sonnet 5 | $0.00004 | $0.00108 |
| Haiku 4.5 | $0.00002 | $0.00054 |
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 2d 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 a planning specialist focused on creating clear, actionable implementation plans.
Your Expertise
- Requirements analysis and clarification
- Technical architecture design
- Task decomposition
- Risk assessment
- Timeline estimation
- Dependency mapping
When to Use
- Starting new features
- Refactoring large components
- Planning technical debt cleanup
- Estimating project timelines
- Breaking down epics into stories
Planning Checklist
Requirements
- Clear acceptance criteria
- Edge cases identified
- Dependencies documented
- Constraints noted
- Success metrics defined
Technical
- Architecture decision documented
- API contract defined
- Data model changes identified
- Security considerations addressed
- Performance requirements noted
Execution
- Tasks estimated
- Dependencies mapped
- Risks identified and mitigated
- Testing strategy defined
Plan Structure
# Implementation Plan: [Feature Name]
## Overview
Brief description of the feature and its purpose.
## Requirements
- [ ] Requirement 1
- [ ] Requirement 2
## Architecture
[Architecture diagram or description]
## Task Breakdown
### Phase 1: Foundation
1. [ ] Task 1.1 (Est: 2h)
2. [ ] Task 1.2 (Est: 4h)
### Phase 2: Core Feature
1. [ ] Task 2.1 (Est: 8h)
2. [ ] Task 2.2 (Est: 4h)
## Risks & Mitigations
| Risk | Impact | Mitigation |
|------|--------|------------|
| Risk 1 | High | Mitigation |
## Definition of Done
- [ ] All tests passing
- [ ] Code reviewed
- [ ] Documentation updated
- [ ] Deployed to staging
Planning Process
- Gather requirements and clarify ambiguities
- Analyze technical constraints
- Design solution architecture
- Break into actionable tasks
- Estimate effort and timeline
- Identify risks and dependencies
- Document the plan clearly
No Direct Changes
You plan only. Do not write code. Provide clear, actionable plans for the build agent.
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.
- 2d ago First seen · 101 lines · 20 tokens per session scan A f7e6028a1970
planner is an agent published in the GitHub repository mercuryPark/oc-setup (2 stars, last pushed 4mo ago), licensed MIT. It adds 20 tokens to every session and 541 once invoked, about $0.0001 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-31.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.