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 skills/jezweb/vite-flare-starter/plan-tasknpx skills add jezweb/vite-flare-starter --skill plan-taskgit clone --depth 1 https://github.com/jezweb/vite-flare-starterWrote 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/skills/jezweb/vite-flare-starter/plan-task)<a href="https://agentmods.dev/skills/jezweb/vite-flare-starter/plan-task"><img src="https://agentmods.dev/badge/skills/jezweb/vite-flare-starter/plan-task.svg" alt="Measured on agentmods" 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 | $0.00044 | $0.00518 |
| Opus 5 | $0.00022 | $0.00259 |
| Sonnet 5 | $0.00009 | $0.00104 |
| Haiku 4.5 | $0.00004 | $0.00052 |
Grade A, and why
plan-task 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 4d 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
Plan Task
When to use
- "Help me plan X"
- "How do I do Y?"
- "What's the best way to approach Z?"
- "Break this down for me"
Steps
-
Clarify the goal — restate it in one sentence. If the goal is fuzzy ("improve my website"), use
ask_questionsto nail down:- What does "done" look like?
- Hard constraints (deadline, budget, must/must-not)
- Resources available (time, skills, tools)
-
Break into steps — produce 5-10 concrete steps. Each step should:
- Start with a verb (Create, Send, Review, Decide, Test)
- Be small enough to complete in one session
- Have a clear "done" state
-
Identify dependencies — note which steps must happen before others. Don't over-sequence — most steps can run in parallel.
-
Estimate effort for each step (S/M/L or hours, depending on context).
-
Display as progress tracker — use
show_progresswith all steps markedupcoming. The user can update status as they work. -
Add a critical path note — one sentence: which 1-2 steps are most likely to delay everything if they slip?
-
Offer to act via
offer_choices:- "Start with step 1"
- "Save this plan to my files"
- "Add a deadline"
- "Adjust the steps"
Style
- Concrete actions, not abstractions ("Draft the brief" not "Think about scope")
- Right level of detail — for a 1-day task, ~5 steps; for a multi-week project, ~10 with sub-steps
- Realistic estimates — pad for uncertainty, especially first steps
What not to do
- Don't generate more than 10 top-level steps — that's a sign you should chunk into phases
- Don't include "research the problem" as a step (that's planning, not the work)
- Don't sequence things that can run in parallel just because they "feel" sequential
- Don't end without a clear first step the user can take right now
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.
- 4d ago First seen · 50 lines · 44 tokens per session scan A 5f38a27a5b86
plan-task is a skill published in the GitHub repository jezweb/vite-flare-starter (48 stars, last pushed 9d ago), licensed MIT. It adds 44 tokens to every session and 518 once invoked, about $0.0002 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…