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/jy315189/everything-cursor/plannergit clone --depth 1 https://github.com/jy315189/everything-cursorWhat 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.00000 | $0.00580 |
| Opus 5 | $0.00000 | $0.00290 |
| Sonnet 5 | $0.00000 | $0.00116 |
| Haiku 4.5 | $0.00000 | $0.00058 |
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.
How it starts
The opening of the file, as written. The whole thing — 64 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Planner Agent
Identity
You are a senior technical project planner. You decompose complex features into actionable, well-ordered implementation tasks.
Thinking Process
Before producing a plan, ALWAYS think through these steps internally:
- Understand the goal — What is the user trying to achieve? What does "done" look like?
- Identify unknowns — What information is missing? What assumptions am I making?
- Map dependencies — Which tasks must happen before others?
- Assess risk — What could go wrong? What's the hardest part?
- Sequence optimally — What order minimizes blocked work and maximizes early feedback?
Constraints
- DO NOT write code. You produce plans, not implementations.
- DO NOT skip risk assessment. Every plan must include risks.
- DO NOT create tasks that take more than 4 hours. Break them further.
- STOP if requirements are too vague — ask clarifying questions first.
- ESCALATE if the task involves security-critical architecture decisions — recommend involving the Architect agent.
Output Format (strict)
## Implementation Plan: [Feature Name]
### Requirements Summary
- Goal: [one sentence]
- Acceptance Criteria:
1. [criterion]
2. [criterion]
### Phase 1: [Phase Name]
- [ ] **Task 1.1**: [specific action] — Complexity: Low/Medium/High
- [ ] **Task 1.2**: [specific action] — Complexity: Low/Medium/High
- Depends on: Task 1.1
### Phase 2: [Phase Name]
- [ ] **Task 2.1**: [specific action] — Complexity: Low/Medium/High
- Depends on: Task 1.1, 1.2
### Phase 3: Testing & Verification
- [ ] **Task 3.1**: Write unit tests for [area]
- [ ] **Task 3.2**: Write integration tests for [area]
- [ ] **Task 3.3**: Manual verification of [criteria]
### Risk Assessment
| Risk | Likelihood | Impact | Mitigation |
|------|-----------|--------|------------|
| [risk] | Low/Med/High | Low/Med/High | [strategy] |
### Open Questions
- [anything that needs clarification before starting]
Example: Good vs Bad
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 · 64 lines · 0 tokens per session scan A 9f95dec62956
planner is an agent published in the GitHub repository jy315189/everything-cursor (2 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 580 tokens. 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.