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/joshidikshant/devsquad/workflow-orchestrationnpx skills add joshidikshant/devsquad --skill workflow-orchestrationgit clone --depth 1 https://github.com/joshidikshant/devsquadWhat 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.00052 | $0.00465 |
| Opus 5 | $0.00026 | $0.00233 |
| Sonnet 5 | $0.00010 | $0.00093 |
| Haiku 4.5 | $0.00005 | $0.00047 |
Grade A, and why
workflow-orchestration 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.
What it actually says
Workflow Orchestration Skill
Chains multiple DevSquad skills into an autonomous, feature-complete workflow that executes with minimal user intervention. Reads a JSON workflow definition file, executes steps sequentially, gates destructive operations with user permission prompts, auto-commits at checkpoints, and validates the result.
When to Use
Use this skill when the user:
- Wants to run a pre-defined multi-step workflow (e.g., "run the feature workflow for issue-42")
- Asks to "chain" multiple skills or automate a sequence of operations
- Mentions a workflow file (e.g., "use feature-workflow.json")
- Wants a repeatable, auditable process for common development patterns
Invocation
bash "${CLAUDE_PLUGIN_ROOT}/skills/workflow-orchestration/scripts/run-workflow.sh" \
--workflow "${CLAUDE_PLUGIN_ROOT}/skills/workflow-orchestration/templates/feature-workflow.json" \
[--dry-run] \
[--skip-gates]
Arguments
| Argument | Required | Description |
|---|---|---|
--workflow <path> |
Yes | Path to the JSON workflow definition file |
--dry-run |
No | Print steps without executing them |
--skip-gates |
No | Skip destructive-step confirmation prompts (use with caution) |
Workflow JSON Format
See templates/feature-workflow.json for a complete example. Each step has:
id- unique step identifier (used as checkpoint key)skill- shell command or script to invokeargs- string of arguments passed to the skilldestructive- boolean, gates with user prompt if truecheckpoint- boolean, auto-commits and records hash if truecommit_message- optional message template (supports$WORKFLOW_NAME,$STEP_IDenv vars)
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 45 lines · 52 tokens per session scan A 5c80eca76b13
workflow-orchestration is a skill published in the GitHub repository joshidikshant/devsquad (7 stars, last pushed 1mo ago), licensed MIT. It adds 52 tokens to every session and 465 once invoked, about $0.0003 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…