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/parkerm2/create-claude-workflow/wf-plannpx skills add ParkerM2/create-claude-workflow --skill wf-plangit clone --depth 1 https://github.com/ParkerM2/create-claude-workflowWrote 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/parkerm2/create-claude-workflow/wf-plan)<a href="https://agentmods.dev/skills/parkerm2/create-claude-workflow/wf-plan"><img src="https://agentmods.dev/badge/skills/parkerm2/create-claude-workflow/wf-plan.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.00024 | $0.00598 |
| Opus 5 | $0.00012 | $0.00299 |
| Sonnet 5 | $0.00005 | $0.00120 |
| Haiku 4.5 | $0.00002 | $0.00060 |
Grade B, and why
wf-plan scanned grade B with 1 finding 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 5d 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
cat .claude/.workflow-state/preflight-complete.json What it actually says
WF: Load Plan
Gate Check
cat .claude/.workflow-state/preflight-complete.json
If the file does not exist: STOP — "Pre-flight not complete. Run Step 1
(wf-preflight) first."
Read the file and load: TICKET, FEATURE_NAME, PLUGIN_ROOT, mode.
Your Task
Parse the task files and produce a validated wave plan before any agents are spawned.
Checklist
1. Read Design Doc (if exists)
ls .claude/progress/<TICKET>/plans/*.md 2>/dev/null
If found, read it for architectural context. If not found, continue.
2. Parse Task Files
ls .claude/progress/<TICKET>/tasks/task-*.md
For each file, extract YAML frontmatter:
taskNumber,taskName,taskSlug,agentRole,agentDefinitionwave,blockedBy,blocks,estimatedTokens,complexity
3. Validate
Check all of the following. If any fail, list ALL failures before stopping:
- Every task has
taskNumber,taskName,taskSlug,wave - No two tasks own the same file path
- Dependency graph is acyclic (
blockedByhas no cycles) - No task exceeds 18,000
estimatedTokens
If validation fails: STOP — list each issue with the task file name.
4. Build Wave Plan
Group tasks by wave number. Sort waves numerically. Record TOTAL_WAVES.
Output a summary table:
Wave 1: task-1 (react-component-agent), task-2 (react-hooks-agent)
Wave 2: task-3 (react-query-agent)
Total: 3 tasks, 2 waves
5. Write Stamp
cat > .claude/.workflow-state/plan-complete.json << EOF
{
"ticket": "<TICKET>",
"totalTasks": <N>,
"totalWaves": <M>,
"taskFiles": ["task-1.md", "task-2.md", ...],
"waveMap": { "1": ["task-1", "task-2"], "2": ["task-3"] },
"currentWave": 1
}
EOF
Emit: /claude-workflow:track plan.created "<N tasks in M waves>"
Done
Report the wave plan summary and say: "Plan loaded. Return to the /agent-team checklist and check Step 2."
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.
- 5d ago First seen · 95 lines · 24 tokens per session scan B a27dac97f0aa
wf-plan is a skill published in the GitHub repository ParkerM2/create-claude-workflow (4 stars, last pushed 5mo ago), licensed MIT. It adds 24 tokens to every session and 598 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). 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.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…