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 skills add shwilliamson/automatasaurus --skill workflow-orchestrationgit clone --depth 1 https://github.com/shwilliamson/automatasaurusWrote 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/shwilliamson/automatasaurus/workflow-orchestration)<a href="https://agentmods.dev/skills/shwilliamson/automatasaurus/workflow-orchestration"><img src="https://agentmods.dev/badge/skills/shwilliamson/automatasaurus/workflow-orchestration.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.00031 | $0.02532 |
| Opus 5 | $0.00015 | $0.01266 |
| Sonnet 5 | $0.00006 | $0.00506 |
| Haiku 4.5 | $0.00003 | $0.00253 |
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 7d 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 — 376 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Workflow Orchestration
This skill defines how the Automatasaurus workflow operates.
Architecture Overview
Slash Commands (Orchestration)
Commands run in the main conversation and orchestrate agents:
| Command | Purpose | Produces |
|---|---|---|
/auto-discovery |
Requirements gathering | discovery.md (or discovery-{N}.md on re-runs), issues |
/auto-plan |
Implementation planning | implementation-plan.md (or implementation-plan-{N}.md on re-runs) |
/auto-evolve |
Generate agent context | PROJECT.md files (fully regenerated each run) |
/auto-clear |
Remove all generated planning files | Clean slate |
/auto-work-issue {n} |
Single issue | PR (user merges) |
/auto-work-all |
All issues | PRs merged, issues closed |
Agents (Autonomous Workers)
Agents perform discrete tasks without user dialogue:
| Agent | Tasks |
|---|---|
developer |
Implements issues, creates PRs |
architect |
Reviews discovery plans, reviews PRs, helps stuck developers |
designer |
Reviews discovery plans, reviews PRs, adds design specs |
tester |
Runs tests, manual verification with Playwright |
Workflow Modes
The system operates in different modes:
| Mode | Command | Merge Behavior |
|---|---|---|
discovery |
/auto-discovery |
N/A - creates issues |
planning |
/auto-plan |
N/A - creates plan |
single-issue |
/auto-work-issue {n} |
Notify only - user merges |
all-issues |
/auto-work-all |
Auto-merge and continue |
Mode Context Passing
When delegating to agents, include mode context:
# Single-issue mode
"This is SINGLE-ISSUE mode. Do NOT auto-merge. Notify when PR is approved."
# All-issues mode
"This is ALL-ISSUES mode. Auto-merge after approvals and continue to next issue."
Default: If mode unclear, default to single-issue (safer).
Coordination Modes
The orchestrator can use two modes for delegating work to agents:
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.
- 7d ago First seen · 376 lines · 31 tokens per session scan A 89c85c20500e
workflow-orchestration is a skill published in the GitHub repository shwilliamson/automatasaurus (5 stars, last pushed 6mo ago), licensed MIT. It adds 31 tokens to every session and 2,532 once invoked, about $0.0002 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
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
monorepo-management
Master monorepo management with Turborepo, Nx, and pnpm workspaces to build efficient, scalable multi-package repositories with optimized builds and dependency management. Use when setting up monorepos, optimizing builds, or managing shared dependencies.