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/using-workflownpx skills add ParkerM2/create-claude-workflow --skill using-workflowgit clone --depth 1 https://github.com/ParkerM2/create-claude-workflowWhat 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.00029 | $0.01129 |
| Opus 5 | $0.00015 | $0.00564 |
| Sonnet 5 | $0.00006 | $0.00226 |
| Haiku 4.5 | $0.00003 | $0.00113 |
Grade A, and why
using-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 — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.
claude-workflow
Multi-agent workflow orchestration for Claude Code. Provides branch-per-task feature development with automated QA, codebase guardian enforcement, and crash recovery.
Commands
| Command | Description |
|---|---|
| /setup-workflow | First-time project setup — config, infrastructure, agent discovery, docs, CLAUDE.md |
| /connect-atlassian | Connect Jira + Confluence — guided API token setup, 72 tools for tickets, sprints, IKTs |
| /agent-team | Execute a pre-planned feature — reads task files from /new-plan, spawns agents with thin prompts |
| /new-plan | Deep technical planning and task decomposition before implementation |
| /deep-research | Conversational deep research with phased investigation and multi-layered validation |
| /resume | Crash recovery — resume from last checkpoint |
| /status | Quick progress summary of active feature |
| /settings | Scan and validate agent definitions, audit performance, manage permissions |
| /track | Emit tracking events to JSONL progress log |
Agents
- team-leader: Orchestrator agent that decomposes features into tasks, delegates to sub-agents, and manages branch lifecycle. Runs the main workflow loop.
- qa-reviewer: Quality gate agent that reviews code changes, runs tests, checks for regressions, and enforces project standards before merge.
- codebase-guardian: Structural integrity agent that monitors for unauthorized changes to protected files, architecture violations, and dependency issues.
Workflow Modes
- strict: Full QA pipeline — every task reviewed by qa-reviewer and codebase-guardian before merge. Best for production codebases.
- standard: Balanced mode — QA reviews on feature completion, Guardian checks on protected files only. Default mode.
- fast: Minimal checks — skip QA reviews, Guardian runs only on final merge. Best for prototyping and spikes.
Configuration
Project configuration lives in .claude/workflow.json. Run /workflow-setup to configure interactively.
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 · 91 lines · 29 tokens per session scan A 3afa721b2087
using-workflow is a skill published in the GitHub repository ParkerM2/create-claude-workflow (4 stars, last pushed 5mo ago), licensed MIT. It adds 29 tokens to every session and 1,129 once invoked, about $0.0001 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…