Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add sequenzia/agent-alchemy/plugin install agent-alchemy-sdd-toolsWrote 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/sequenzia/agent-alchemy/run-tasks)<a href="https://agentmods.dev/skills/sequenzia/agent-alchemy/run-tasks"><img src="https://agentmods.dev/badge/skills/sequenzia/agent-alchemy/run-tasks.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.00018 | $0.03684 |
| Opus 5 | $0.00009 | $0.01842 |
| Sonnet 5 | $0.00004 | $0.00737 |
| Haiku 4.5 | $0.00002 | $0.00368 |
Grade A, and why
run-tasks 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 4d 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 — 256 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Run Tasks Skill
This skill orchestrates autonomous task execution using Claude Code's native Agent Team system. It takes tasks produced by /create-tasks, builds a dependency-aware execution plan, and executes them in waves via a 3-tier agent hierarchy: Orchestrator (this skill) plans and coordinates waves, Wave Leads manage parallel executors within each wave, and Context Managers handle knowledge flow between tasks.
The wave-lead creates its own team and coordinates teammates via SendMessage. The orchestrator communicates with the wave-lead via file-based summaries (wave-{N}-summary.md).
Load Reference Skills
Before executing any step, load the foundational references for task management and team orchestration:
Tasks Reference
Read ${CLAUDE_PLUGIN_ROOT}/../claude-tools/skills/claude-code-tasks/SKILL.md
Teams Reference
Read ${CLAUDE_PLUGIN_ROOT}/../claude-tools/skills/claude-code-teams/SKILL.md
These references provide tool parameters, lifecycle rules, messaging protocols, and orchestration patterns. The SDD-specific execution procedures are in the orchestration reference below.
Orchestration Patterns Reference (optional, for context)
Read ${CLAUDE_PLUGIN_ROOT}/../claude-tools/skills/claude-code-teams/references/orchestration-patterns.md
Orchestration Reference
Read ${CLAUDE_PLUGIN_ROOT}/skills/run-tasks/references/orchestration.md
If any reference file cannot be read, stop and report: "ERROR: Cannot load required reference. Verify the plugin installation is complete."
Argument Parsing
Parse the following arguments from the user's invocation:
| Argument | Format | Default | Description |
|---|---|---|---|
<task-id> |
positional integer | (none — all tasks) | Execute a single specific task by ID. Mutually exclusive with --task-group and --phase. |
--task-group |
<name> |
(none — all tasks) | Filter tasks to those with matching metadata.task_group |
--phase |
<N> or <N,M,...> |
(none — all phases) | Comma-separated integers. Filter tasks by metadata.spec_phase. Tasks without spec_phase are excluded when active. |
--max-parallel |
<N> |
(from settings) | Override run-tasks.max_parallel setting for this run. Must be a positive integer. |
--retries |
<N> |
(from settings) | Override run-tasks.max_retries setting for this run. Must be a non-negative integer (0 = no retries). |
--dry-run |
(flag) | false |
Complete Steps 1-3 only: load, plan, display. No agents spawned, no session directory created. |
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.
- 4d ago First seen · 256 lines · 18 tokens per session scan A d4a2a7dbeaf8
run-tasks is a skill published in the GitHub repository sequenzia/agent-alchemy (44 stars, last pushed 3mo ago), licensed MIT. It adds 18 tokens to every session and 3,684 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-09-03.
Other skills, from other repositories
execute-round
Use when a planned round handoff exists and needs to be implemented end-to-end via the 4-commit chain (entry-admin → BA design → dev body with inline CR + SE → state refresh + self-audit). Dispatches ba-designer / developer / cr-reviewer / se-contract sequentially.
status
Render the feature × stage integrity matrix — every feature vs every Iron Law stage with pass/skip/fail markers. Use when the user wants a project-wide status board, a release-readiness view, or to spot which features are still behind which stage. Activate only when the connected project contains spec.yaml or the user…
debt-ops-add
Register a deferred decision in the tech-debt registry. Trigger by judgment, not a marker scan, whenever a future reader would ask "why this way?": an unmade decision, stub, loosened type, bypassed check, swallowed error, a default picked "for now", or a TODO/FIXME/HACK/XXX marker. Trigger immediately whenever you…
retro
Engineering retrospective from git metrics. Reports deployment frequency, release cycle span, churn hotspots, backlog health. Outputs narrative report with 3+ actionable items. Flags: --since, --path, explicit range argument.
ccc-onboard
CC Commander contributor onboarding workflow. Detects project conventions, asks for contributor role, builds a tailored first-hour checklist, starter links, and…
backlog
Manage the project's tech debt backlog. Add, list, fix, wontfix, delete, prioritize, and suggest batch actions on tracked issues. Used by audit and review skills to persist findings, and directly by users to manage accumulated debt. Modes: list [category], add [description], fix B-{N}, wontfix B-{N} [reason], delete…