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/hknc/claude-evolve/prepare-tasknpx skills add hknc/claude-evolve --skill prepare-taskgit clone --depth 1 https://github.com/hknc/claude-evolveWrote 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/hknc/claude-evolve/prepare-task)<a href="https://agentmods.dev/skills/hknc/claude-evolve/prepare-task"><img src="https://agentmods.dev/badge/skills/hknc/claude-evolve/prepare-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.00086 | $0.02292 |
| Opus 5 | $0.00043 | $0.01146 |
| Sonnet 5 | $0.00017 | $0.00458 |
| Haiku 4.5 | $0.00009 | $0.00229 |
Grade A, and why
prepare-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 3d 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 — 307 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Prepare Task Skill
Analyze the current task and proactively create missing agents/skills in the user's toolkit.
When to Use
- Before complex tasks that might benefit from specialized agents
- When user wants to optimize their toolkit for a specific domain
- After creating a plan, before execution
- When starting work that would benefit from workflow guidance
Workflow
1. Gather Task Context
Read the current conversation to understand:
- What task is the user trying to accomplish?
- What technologies/domains are involved?
- What operations are needed (debugging, refactoring, testing, etc.)?
If a plan exists in the conversation, analyze its steps.
2. Assess Task Depth
Evaluate complexity signals to determine how much preparation is warranted:
| Signal | Low | Medium | High |
|---|---|---|---|
| Scope | Single operation | Multi-step | Multi-system |
| Stakes | Reversible | Has rollback | Irreversible |
| Clarity | Explicit requirements | Some gaps | Undefined |
| Familiarity | Known | Partially known | New territory |
Map to depth:
execute(all low) -> Skip toolkit recommendations entirelycheck(mixed low) -> Skip toolkit recommendationsplan(mixed medium) -> Recommend only high-impact gapsdesign(multiple high) -> Full gap analysis + workflow suggestionexplore(high stakes + unclear) -> Full analysis + research suggestions
For execute/check tasks: Output only:
[claude-evolve] Task is straightforward - no toolkit gaps to address.
See ${CLAUDE_PLUGIN_ROOT}/skills/prepare-task/references/depth-patterns.md for detailed signal assessment heuristics, override rules, and AskUserQuestion templates.
3. Discover Toolkit Capabilities
Find the active toolkit:
TOOLKIT_NAME=$(cat $HOME/.claude-evolve/active 2>/dev/null)
TOOLKIT_PATH=$HOME/.claude-evolve/toolkits/$TOOLKIT_NAME
List existing agents (FLAT structure):
ls $TOOLKIT_PATH/agents/*.md 2>/dev/null
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 3d ago First seen · 307 lines · 86 tokens per session scan A 1d5c07135cc3
prepare-task is a skill published in the GitHub repository hknc/claude-evolve (8 stars, last pushed 7mo ago), licensed MIT. It adds 86 tokens to every session and 2,292 once invoked, about $0.0004 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 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…