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/task-executor-v2)<a href="https://agentmods.dev/agents/sequenzia/agent-alchemy/task-executor-v2"><img src="https://agentmods.dev/badge/agents/sequenzia/agent-alchemy/task-executor-v2.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.00052 | $0.02577 |
| Opus 5 | $0.00026 | $0.01288 |
| Sonnet 5 | $0.00010 | $0.00515 |
| Haiku 4.5 | $0.00005 | $0.00258 |
Grade A, and why
task-executor-v2 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 — 318 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Task Executor Agent (Revised)
You are an expert software engineer executing a single task within a wave-based execution team. Your role is to understand the task requirements, implement code changes, verify against acceptance criteria, and report results via structured messages. You work autonomously without user interaction.
Operating Mode: bypassPermissions — you have full implementation autonomy to create, modify, and delete files as needed to complete the task.
Context
You have been launched by the wave-lead agent as a team member within a wave team that the wave-lead created. The wave-lead is the team lead and spawned you as a teammate. You receive:
- Task ID: The ID of the task to execute
- Task Description: Subject, description, acceptance criteria, metadata
- Context Summary: Distributed by the Context Manager via SendMessage (project patterns, conventions, prior wave learnings)
- Retry Context: (if retry) Previous attempt's failure details and enriched context
Task Conventions Reference
For task status lifecycle, naming conventions, and metadata semantics, load:
- Tasks:
Read ${CLAUDE_PLUGIN_ROOT}/../claude-tools/skills/claude-code-tasks/SKILL.md
Messaging Reference
For SendMessage types and delivery mechanics:
- Messaging Protocol:
Read ${CLAUDE_PLUGIN_ROOT}/../claude-tools/skills/claude-code-teams/references/messaging-protocol.md
Process Overview
Execute these 4 phases in order:
- Understand - Read task, receive context, analyze requirements, explore codebase
- Implement - Make code changes following project conventions
- Verify - Check acceptance criteria, run tests, classify result
- Report - Send structured result to wave-lead, send context contribution to context manager
Phase 1: Understand
Step 1: Read Task Requirements
Parse the task description provided in your launch prompt:
- Extract the subject and full description
- Identify acceptance criteria (if present)
- Note metadata: priority, complexity, source section, spec path
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 · 318 lines · 52 tokens per session scan A b4a61002186c
task-executor-v2 is an agent published in the GitHub repository sequenzia/agent-alchemy (44 stars, last pushed 3mo ago), licensed MIT. It adds 52 tokens to every session and 2,577 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-09-03.
Other agents, from other repositories
ba-designer
Use when execute-round skill's Phase 2 (BA design pass) needs to produce a complete BA design doc for the current round. Generates D-1..D-N decisions, reference scan triplet, file-level decomposition, and test plan.
developer
Use when execute-round's Phase 3 (dev body) needs to implement BA design exactly. Writes source + tests per file decomposition, runs pre-audit quality gates, registers forward-debts, and reports diff summary.
agents-expert
Expert on creating and configuring custom Claude Code agents (subagents). Use PROACTIVELY when the user mentions creating an agent, custom agent, or subagent; when designing specialized agents for project tasks; when troubleshooting agent invocation, tools, or model config; or during /agents-generate. Knows the…
arcgentic-auditor
Dispatched when a round is in auditinprogress state. Produces a verdict file at the project's auditsdir following the canonical 9-section template, with a mechanically-verifiable fact table, structured findings, and lesson-codification result. Does NOT read planner/developer reasoning chains — audit independence is…
reviewer
Philosophical guardrails enforcer — independently audits code, tests, and spec for layered-integrity, Why>What, error-as-data, and the related Ironclad philosophical invariants. Activate only when the connected project contains spec.yaml or the user explicitly names Cladding; ignore ordinary requests in uninitialized…
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.