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/workflownpx skills add hknc/claude-evolve --skill workflowgit clone --depth 1 https://github.com/hknc/claude-evolveWhat 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.00168 | $0.01912 |
| Opus 5 | $0.00084 | $0.00956 |
| Sonnet 5 | $0.00034 | $0.00382 |
| Haiku 4.5 | $0.00017 | $0.00191 |
Grade A, and why
workflow 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 — 171 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Workflow Skill
Manage active multi-phase development workflows using native Claude Code tasks. This skill covers core behavior — routing, status display (including phase-specific guidance), phase transitions, spec doc sync, and acceptance criteria verification. For implementation details (sub-task creation, dependency analysis, pivot handling), see ${CLAUDE_PLUGIN_ROOT}/commands/workflow.md.
Routing
Route based on user intent:
| Input | Action |
|---|---|
/workflow or "show my workflow" |
Show current phase and progress |
/workflow next or "next phase" |
Advance to next phase |
/workflow skip or "skip phase" |
Skip current phase |
/workflow done or "workflow done" |
Mark workflow complete |
/workflow switch or "switch workflow" |
Switch between active workflows |
/workflow expand |
Create sub-tasks from phase items |
| Natural-language status queries (e.g., "where am I", "what should I do next") | Show current phase and progress (same as /workflow) |
Execution
1. Find Current Workflow
CALL TaskList to find tasks with [claude-evolve] prefix.
- One found: Use as current workflow
- Multiple found: List them and let user pick, or suggest
/workflow switch - None found: Show fallback (see Error Handling)
2. Show Status
CALL TaskGet(id) to read task details and metadata.
Read metadata fields: depth, phase, phases_done, phases_skipped, has_phase_tasks, spec_file.
If depth is execute (no phases):
[claude-evolve] Workflow: {subject}
Status: In progress (execute — no phases)
{Task description summary}
Commands: done
Otherwise (depths with phases — design, explore, plan, check):
[claude-evolve] Workflow: {subject}
Phase: {current} | Progress: requirements [OK] -> design [OK] -> implement <- testing
{Phase-specific guidance — see table below}
Commands: next | skip | done
Phase-specific guidance:
| Phase | Guidance |
|---|---|
requirements |
Gathering requirements. Ask clarifying questions. |
design |
Planning approach. Consider architecture and patterns. |
implement |
Building the feature. Write code, run tests. |
testing |
Verifying quality. Test edge cases, review code. |
verify |
Quick sanity check. Confirm basics work. |
research |
Investigating options. Explore approaches. |
prototype |
Building proof of concept. Quick and dirty is OK. |
evaluate |
Assessing results. Compare approaches. |
decide |
Committing to direction. Make the call. |
action |
Taking action. Execute the plan. |
outcome |
Checking outcome. Verify results. |
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 · 171 lines · 168 tokens per session scan A a95ab995fb84
workflow is a skill published in the GitHub repository hknc/claude-evolve (8 stars, last pushed 7mo ago), licensed MIT. It adds 168 tokens to every session and 1,912 once invoked, about $0.0008 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.
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…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
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.