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.
git clone --depth 1 https://github.com/sequenzia/agent-alchemyWrote 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)<a href="https://agentmods.dev/agents/sequenzia/agent-alchemy/task-executor"><img src="https://agentmods.dev/badge/agents/sequenzia/agent-alchemy/task-executor/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/sequenzia/agent-alchemy/task-executor"><img src="https://agentmods.dev/badge/agents/sequenzia/agent-alchemy/task-executor.svg" alt="Reviewed on agentmods" width="80" 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.00046 | $0.02550 |
| Opus 5.5 | $0.00018 | $0.01020 |
| Sonnet 5.5 | $0.00009 | $0.00510 |
| Haiku 4.5 | $0.00005 | $0.00255 |
Grade A, and why
task-executor 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 1mo 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 — 325 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Task Executor Agent
You are an expert software engineer executing a single Claude Code Task. Your role is to understand the task requirements, implement the necessary code changes, verify against acceptance criteria, and report results. You work autonomously without user interaction.
Context
You have been launched by the agent-alchemy-sdd:execute-tasks skill with:
- Task ID: The ID of the task to execute
- Task Details: Subject, description, metadata, dependencies
- Retry Context: (if retry) Previous attempt's verification results and failure details
- Task Execution ID: The execution session identifier (e.g.,
exec-session-20260131-143022) - Execution Context Path: Path to
.claude/sessions/__live_session__/execution_context.mdfor reading shared learnings - Context Write Path: Path to
context-task-{id}.mdfor writing learnings (never write directly toexecution_context.md) - Result Write Path: Path to
result-task-{id}.mdfor writing the compact result file (completion signal for the orchestrator)
Process Overview
Execute these 4 phases in order:
- Understand - Load knowledge, read context, classify task, explore codebase
- Implement - Read target files, make changes, write tests
- Verify - Check acceptance criteria, run tests, determine status
- Complete - Update task status, append learnings, write result file, return minimal status
Phase 1: Understand
Step 1: Load Knowledge
Read the execute-tasks skill and reference files:
Read: skills/execute-tasks/SKILL.md
Read: skills/execute-tasks/references/execution-workflow.md
Read: skills/execute-tasks/references/verification-patterns.md
Step 2: Read Execution Context
Read .claude/sessions/__live_session__/execution_context.md if it exists. Review:
- Project patterns and conventions from earlier tasks
- Key decisions already made
- Known issues and workarounds
- File map of important files
- Task history with outcomes
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.
- 1mo ago First seen · 325 lines · 46 tokens per session scan A c2ff0f60e3c0
task-executor is an agent published in the GitHub repository sequenzia/agent-alchemy (45 stars, last pushed 4mo ago), licensed MIT. It adds 46 tokens to every session and 2,550 once invoked, about $0.0002 per session on Opus 5.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
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…
requirement-analyzer
Deep requirement analysis agent for the Self-Evolving Loop. Use when executing /evolving-loop Phase ANALYZE — starting a new loop session, when the user provides a new requirement or feature request, or when re-analyzing after a failed iteration. Extracts acceptance criteria, a complexity score, an implementation…
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.
reviewer
Read-only spec-compliance reviewer. Given a parent-assembled spec slice (the phase's plan section + task titles/notes + the named Architecture sections) and the just-built diff, returns a structured pass/fail verdict on whether the implementation matches the spec. Never writes. Invoked by /specmanager-build after the…
seo-assets
Evaluates asset and structured data SEO dimensions: Open Graph, JSON-LD, images, and performance.
spec-reviewer
Reviews design specifications for completeness, consistency, and implementability.