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-qa-gatenpx skills add ParkerM2/create-claude-workflow --skill wf-qa-gategit 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-qa-gate)<a href="https://agentmods.dev/skills/parkerm2/create-claude-workflow/wf-qa-gate"><img src="https://agentmods.dev/badge/skills/parkerm2/create-claude-workflow/wf-qa-gate.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.1 | $0.00034 | $0.01084 |
| Opus 5 | $0.00017 | $0.00542 |
| Sonnet 5 | $0.00007 | $0.00217 |
| Haiku 4.5 | $0.00003 | $0.00108 |
Grade B, and why
wf-qa-gate 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/wave-<currentWave>-spawned.json How it starts
The opening of the file, as written. The whole thing — 135 lines — stays where its author put it; the contents beside it link to each section on GitHub.
WF: QA Gate
Gate Check
cat .claude/.workflow-state/wave-<currentWave>-spawned.json
Determine currentWave from setup-complete.json. If spawn stamp missing:
STOP — "Wave not spawned. Run Step 4a (wf-spawn) first."
Load agent IDs, task list, TICKET, TEAM_LEADER_NAME, workPrefix,
worktreeDir, featureBranch from state files.
Your Task
Wait for coder completions, coordinate QA, and merge each passing task. Do not move to the next wave until ALL tasks in this wave are merged.
Checklist
1. Wait for Coder Completions
Wait for each coder-task-<N> to SendMessage with completion. When a coder
reports done:
- Note which task completed and which files changed
- Notify QA:
SendMessage(to: "qa-task-<N>", message: "Code ready. Files: <list>.")
RECOVERY: If a coder goes silent for >5 minutes, send one nudge. If no response after 2 minutes, check
TaskOutput. If crashed, spawn a replacement on the same worktree with the same task file.
2. Handle QA Verdict
On PASS:
- Emit:
/claude-workflow:track qa.passed "Task #<N>" --task <N> - Rebase and merge:
git -C <worktreePath> rebase <featureBranch> git checkout <featureBranch> git merge --no-ff <workbranch> -m "Merge <taskSlug>: <summary>" - Emit:
/claude-workflow:track branch.merged "<taskSlug> to feature" - Cleanup:
git worktree remove <worktreePath> git branch -d <workbranch> - Shut down both agents:
SendMessage(to: "coder-task-<N>", message: {"type": "shutdown_request"}) SendMessage(to: "qa-task-<N>", message: {"type": "shutdown_request"}) - Update task file:
status→"complete"
On FAIL (round < 3):
- Emit:
/claude-workflow:track qa.failed "Task #<N>, round <R>" --task <N> - Forward to coder:
SendMessage(to: "coder-task-<N>", message: "QA FAIL round <R>. Issues: <list>") - Wait for coder to fix and message back
- Shut down previous QA agent
- Spawn NEW QA:
name: "qa-task-<N>-r<round>"with same template - Wait for new verdict. Increment round. Repeat from step 1.
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 · 135 lines · 34 tokens per session scan B bea57c757c47
wf-qa-gate is a skill published in the GitHub repository ParkerM2/create-claude-workflow (4 stars, last pushed 5mo ago), licensed MIT. It adds 34 tokens to every session and 1,084 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.
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…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
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…
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…