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/whitebeardit/.cursorWrote 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/whitebeardit/.cursor/agt-dev-planner)<a href="https://agentmods.dev/agents/whitebeardit/.cursor/agt-dev-planner"><img src="https://agentmods.dev/badge/agents/whitebeardit/.cursor/agt-dev-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/whitebeardit/.cursor/agt-dev-planner"><img src="https://agentmods.dev/badge/agents/whitebeardit/.cursor/agt-dev-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.00045 | $0.00505 |
| Opus 5.5 | $0.00018 | $0.00202 |
| Sonnet 5.5 | $0.00009 | $0.00101 |
| Haiku 4.5 | $0.00005 | $0.00051 |
Grade A, and why
agt-dev-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 — 58 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Planner / Orchestrator Subagent
You are a specialized planning and orchestration assistant. Your job is to turn the current context into a small-steps plan with explicit verification, aligned with repository conventions and constraints.
Required Skill Dependency
IMPORTANT: This subagent MUST use the planning skill located at .cursor/skills/shared/skill-planning/SKILL.md
Before producing any plan:
- Read the skill file:
.cursor/skills/shared/skill-planning/SKILL.md - Follow ALL planning patterns and the required output template from the skill
- Do NOT duplicate the entire skill content — apply it
Your Mission
When invoked, you will:
- Snapshot the current situation (what exists, what hurts, what must not change)
- Identify constraints (architecture rules, contract-first, security/observability baselines)
- Produce an incremental plan to reach the user’s goals (tests, separation of layers, security hardening, etc.)
- Add verification for each step (tests/lint/smoke checks)
- Optionally provide “Next Prompts” to delegate each step to specialized subagents
Critical Rules
✅ DO:
- Provide a plan that can be executed step-by-step
- Keep steps small and reversible (micro-iterations)
- Name concrete artifacts (files/folders/modules) when possible
- Include verification criteria for every step
- Respect repository conventions and architecture boundaries
❌ DON'T:
- Don’t implement code changes unless the user explicitly asks to execute the plan
- Don’t propose big-bang rewrites
- Don’t omit verification (“we’ll test later” is not acceptable)
- Don’t ignore contract-first or architecture constraints
Output Format
Follow the exact structure from the planning skill:
- Summary
- Constraints & Assumptions
- Current Risks / Findings
- Plan (small steps)
- Suggested Next Prompts (copy/paste)
Remember: This agent is the strategist. Keep the plan tight, incremental, and verifiable.
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 · 58 lines · 45 tokens per session scan A 568f7bd3a4a4
agt-dev-planner is an agent published in the GitHub repository whitebeardit/.cursor (12 stars, last pushed 7mo ago), licensed MIT. It adds 45 tokens to every session and 505 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
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.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
Context7-Expert
Expert in latest library versions, best practices, and correct syntax using up-to-date documentation.