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/lerianstudio/ring/dispatching-workflowsnpx skills add LerianStudio/ring --skill dispatching-workflowsgit clone --depth 1 https://github.com/LerianStudio/ringWhat 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.00142 | $0.03156 |
| Opus 5 | $0.00071 | $0.01578 |
| Sonnet 5 | $0.00028 | $0.00631 |
| Haiku 4.5 | $0.00014 | $0.00316 |
Grade A, and why
ring:dispatching-workflows 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 — 181 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Dispatching Workflows
When to use
- A phased plan exists (typically from ring:writing-plans) and you want each phase executed by a multi-agent harness, not a single subagent
- You want review and an adversarial contrarian pass baked inside every wave — verified work returns, unverified work does not
- Work benefits from phase checkpoints and supervisor course-correction between phases
Skip when
- One supervised subagent per wave is enough → ring:executing-plans (lighter; the supervisor reviews after the wave returns)
- Production work needing the full gated specialist roster and Gate 0/8/9 → ring:running-dev-cycle
- No plan exists yet → ring:writing-plans first
- Plan covers multiple independent subsystems → split into separate plans before executing
Sequence
Runs after: ring:writing-plans (consumes and updates its living plan document) Alternatives: ring:executing-plans (one supervised subagent per wave — lighter), ring:running-dev-cycle (full gated specialist cycle — heavier)
Related
Companion skills: ring:writing-plans (Task Format + phase-epic-task hierarchy used during elaboration), ring:test-driven-development (RED→GREEN per task, inside the harness), ring:committing-changes (closes each task with a signed atomic commit), ring:reviewing-code (the full 9+ reviewer pool — run it at plan close or for a high-stakes phase)
The loop: elaborate the current phase into tasks against the real landed code → launch the phase as one workflow that implements, reviews, and contrarian-verifies internally → the workflow returns verified work → review it as supervisor → phase checkpoint → roll to the next phase → repeat. The main agent stays the supervisor; the workflow is a multi-agent harness, not a lone implementer. The plan document is the living source of truth — elaboration writes tasks back into it.
Announce at start: "Using ring:dispatching-workflows to execute this plan phase-by-phase as reviewed multi-agent workflows."
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 · 181 lines · 142 tokens per session scan A faed759b45bd
ring:dispatching-workflows is a skill published in the GitHub repository LerianStudio/ring (210 stars, last pushed 13d ago), licensed Apache-2.0. It adds 142 tokens to every session and 3,156 once invoked, about $0.0007 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-30.
Other skills, from other repositories
agent-benchmark
Self-benchmark: YOU write the code, adversarial reviews it (multi-provider), you fix, you write tests, adversarial reviews tests, you fix. Measures YOUR quality as an agent. Run in different models (Opus, Sonnet, Haiku) and compare results.
explain
/explain - Execution Explainer.
auto
Auto Pilot - Master Workflow Orchestrator.
fixer
Auto-remediation router and retry coordinator.
delegate
Use this agent when you need to coordinate and manage complex workflows involving multiple specialized agents.
guardloop
/guardloop — Adaptive Learning Guardrail Engine.