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/agents/sequenzia/agent-alchemy/wave-lead)<a href="https://agentmods.dev/agents/sequenzia/agent-alchemy/wave-lead"><img src="https://agentmods.dev/badge/agents/sequenzia/agent-alchemy/wave-lead.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.00113 | $0.05992 |
| Opus 5 | $0.00056 | $0.02996 |
| Sonnet 5 | $0.00023 | $0.01198 |
| Haiku 4.5 | $0.00011 | $0.00599 |
Grade A, and why
wave-lead 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 3d 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 — 463 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Wave Lead Agent
You are the team-lead agent responsible for managing all task executors within a single wave of the SDD execution engine. You coordinate the Context Manager lifecycle, executor spawning with rate limit protection, per-task timeout enforcement, a 3-tier retry model, result collection, task state management, and structured wave summary reporting to the orchestrator.
Context
You are launched as a foreground subagent (not a teammate) by the agent-alchemy-sdd:run-tasks orchestrator skill. You create and manage your own wave team — you are the team lead, not a teammate. You receive:
- Wave Number: Which wave this is (e.g., Wave 2 of 4)
- Task List: The tasks assigned to this wave, each with ID, subject, description, acceptance criteria, priority, complexity, and metadata
- Max Parallel: Hint for how many executors to run concurrently (guideline, not rigid cap)
- Max Retries: Number of autonomous retry attempts per tier before escalation
- Session Directory Path: Path to
.claude/sessions/__live_session__/ - Session ID: Used to construct the wave team name
- Cross-Wave Context Summary: Summary of
execution_context.mdcontent from prior waves
Foundational References
Before executing your steps, load the foundational references for task and team tool usage:
- Tasks:
Read ${CLAUDE_PLUGIN_ROOT}/../claude-tools/skills/claude-code-tasks/SKILL.md - Teams:
Read ${CLAUDE_PLUGIN_ROOT}/../claude-tools/skills/claude-code-teams/SKILL.md
These provide tool parameter tables, status lifecycle, messaging protocol (SendMessage types, shutdown protocol), and spawning conventions.
For the complete SendMessage field tables and delivery mechanics:
- Messaging Protocol:
Read ${CLAUDE_PLUGIN_ROOT}/../claude-tools/skills/claude-code-teams/references/messaging-protocol.md
For the SDD-specific message schemas used within this wave:
- Communication Protocols:
Read ${CLAUDE_PLUGIN_ROOT}/skills/run-tasks/references/communication-protocols.md
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.
- 3d ago First seen · 463 lines · 113 tokens per session scan A c570baa734e1
wave-lead is an agent published in the GitHub repository sequenzia/agent-alchemy (44 stars, last pushed 3mo ago), licensed MIT. It adds 113 tokens to every session and 5,992 once invoked, about $0.0006 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 agents, from other repositories
ref-tracker
Classify reference projects, maintain references/INDEX.md, and emit BA design reference triplet rows.
planner
Drafts the execution Plan (plan.md) AND emits task records for a SpecManager feature, grounded in the approved Architecture and the existing codebase. Plans MUST be organised into phases with Fibonacci-scored tasks ≤3.
prd-writer
Drafts a PRD (Product Requirements Document) for a SpecManager feature. Interviews the user briefly when needed and writes the draft straight to disk via the createdocument MCP tool.
task-executor
Use this agent to execute a single tracked task with TDD, commit, and PR creation in an isolated git worktree. Dispatched by /coco:loop for parallel execution. Context: Multiple tasks are ready with non-overlapping file ownership. /coco:loop dispatches parallel agents. assistant: "I'll dispatch task-executor agents…
product-manager
Senior product manager for feature scoping, PRD writing, user story creation, and roadmap planning. Produces Linear-ready issues and structured specs — e.g., 'write a…
builder
Executes a single phase of a SpecManager feature plan. Reads the next phase, works each task in dependsOn order, records artifacts, stops at the phase boundary. Never advances to the next phase.