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-setupnpx skills add ParkerM2/create-claude-workflow --skill wf-setupgit 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-setup)<a href="https://agentmods.dev/skills/parkerm2/create-claude-workflow/wf-setup"><img src="https://agentmods.dev/badge/skills/parkerm2/create-claude-workflow/wf-setup.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.00038 | $0.01338 |
| Opus 5 | $0.00019 | $0.00669 |
| Sonnet 5 | $0.00008 | $0.00268 |
| Haiku 4.5 | $0.00004 | $0.00134 |
Grade B, and why
wf-setup 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 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.
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/plan-complete.json How it starts
The opening of the file, as written. The whole thing — 187 lines — stays where its author put it; the contents beside it link to each section on GitHub.
WF: Team Setup
Gate Check
cat .claude/.workflow-state/plan-complete.json
If the file does not exist: STOP — "Plan not loaded. Run Step 2
(wf-plan) first."
Load: TICKET, TOTAL_WAVES, waveMap, task file list. Also reload
preflight-complete.json for PLUGIN_ROOT, mode, currentBranch,
featurePrefix, workPrefix, worktreeDir, useWorktrees.
Your Task
Create the team, prepare task files with runtime values, create worktrees,
and inject a CLAUDE.md into each worktree.
Checklist
1. TeamCreate
TeamCreate: team_name = "<TICKET>"
After creation, read team config to get your own name:
cat ~/.claude/teams/<TICKET>/config.json
Extract your TEAM_LEADER_NAME from the members array. Store it.
2. Clean Stale State
git worktree list --porcelain \
| grep "worktree.*<worktreeDir>/<TICKET>" \
| awk '{print $2}' \
| xargs -r -I{} git worktree remove --force {}
git branch --list "<workPrefix>/<TICKET>/*" \
| xargs -r git branch -D
3. Update Task Files with Runtime Values
For each task-*.md file, update YAML frontmatter:
teamLeaderName→TEAM_LEADER_NAMEteamName→TICKETworkbranch→<workPrefix>/<TICKET>/<taskSlug>worktreePath→<worktreeDir>/<TICKET>/<taskSlug>status→"pending"
4. TaskCreate with Dependencies
For each task, call TaskCreate with description + acceptance criteria from
the task file. Then call TaskUpdate with addBlockedBy for each entry in
the task's blockedBy field.
5. Create Worktrees (Wave 1 only)
For each task in Wave 1:
git worktree add <worktreeDir>/<TICKET>/<taskSlug> \
-b <workPrefix>/<TICKET>/<taskSlug>
If useWorktrees is false, create branches instead and continue with
sequential execution.
6. Inject CLAUDE.md into Each Worktree
For each Wave 1 task worktree, write
<worktreeDir>/<TICKET>/<taskSlug>/CLAUDE.md:
# Task #{taskNumber}: {taskName}
You are **{agentRole}** on team "{teamName}".
Workbranch: `{workbranch}`.
## Agent Protocol
{paste full contents of agents/{agentRole}.md — minus YAML frontmatter}
## Task Requirements
{paste task file body: acceptance criteria, file scope, rules,
implementation notes}
## Workflow Phases
Read `{PLUGIN_ROOT}/prompts/implementing-features/AGENT-WORKFLOW-PHASES.md`
and follow Phases 1–4.
## Communication
- Report ONLY to "{TEAM_LEADER_NAME}" via SendMessage.
- Do NOT message other agents. Do NOT spawn agents.
- On completion: SendMessage(to: "{TEAM_LEADER_NAME}",
message: "Task #{taskNumber} complete. Files: <list>. Self-review passed.")
- On blocker: message leader immediately.
- Wait for shutdown_request when done.
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 · 187 lines · 38 tokens per session scan B f6a58b12785f
wf-setup is a skill published in the GitHub repository ParkerM2/create-claude-workflow (4 stars, last pushed 5mo ago), licensed MIT. It adds 38 tokens to every session and 1,338 once invoked, about $0.0002 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.
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…