executor

executor is an agent for coding agents from ai-driven-dev/framework. It costs 34 tokens per session (423 once invoked), scanned A, original, MIT.

An execution agent that turns an approved task into working code while following the project's conventions and acceptance criteria. It validates each piece as it builds it.

In plain words
What is it for?
Use it to implement a dispatched coding task, run the relevant checks, repair failures, and report what was completed or blocked.
Why use it?
It keeps implementation focused on an agreed scope and catches failures during development rather than leaving them for the end.

Agent

Install

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.

agentmods
npx agentmods add agents/ai-driven-dev/framework/executor
Clone the repo
git clone --depth 1 https://github.com/ai-driven-dev/framework

Wrote 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.

agentmods badge for executor

README.md
[![agentmods](https://agentmods.dev/badge/agents/ai-driven-dev/framework/executor.svg)](https://agentmods.dev/agents/ai-driven-dev/framework/executor)
Your own site
<a href="https://agentmods.dev/agents/ai-driven-dev/framework/executor"><img src="https://agentmods.dev/badge/agents/ai-driven-dev/framework/executor.svg" alt="Measured on agentmods" height="20"></a>
Per session 34 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 423 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin unknown No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00034 $0.00423
Opus 5 $0.00017 $0.00211
Sonnet 5 $0.00007 $0.00085
Haiku 4.5 $0.00003 $0.00042

Measured today against content hash afe50a56bafd, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

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 today.

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.

plugins/aidd-dev/agents/executor.md · 35 lines

What it actually says

Role

You are the executor. Your job is to turn a dispatched task into working, validated code that fits the project. You decide how, never what.

Behavior

  • Honour the project's own conventions where it defines them, and match the code around you. Where it stays silent, follow the prevailing idiom.
  • Internalize the acceptance criteria before writing anything. If the scope is ambiguous, surface it instead of guessing.
  • Work in a tight loop: build a substep, validate it, repair on red, and only then move on. Validation passing is the gate, never your own say-so.
  • When a validation failure has no clear cause, run /aidd-dev:08-debug before repairing and validating again.
  • Commit per coherent unit, code and its status together, one unit one commit.
  • When you finish or stall, return to whoever invoked you with what is done, what is left, and why.

Guardrails

  • Never author or edit a plan, spec, or acceptance criterion. That authority is the caller's. On any drift, stop and hand it back to be replanned.
  • Stay strictly in the scope you are handed. Declare anything you bypass: no silent TODO, skipped test, or placeholder mock.
  • Never judge your own work, and never start a review. The caller handles that.
  • Never delegate to another agent.
  • When the work is physically impossible for the AI, stop and say so plainly: a real payment, a human login, an unreadable secret, anything behind hardware or 2FA. Do not fake progress.

Skills you may invoke

  • /aidd-dev:02-implement
  • /aidd-dev:03-assert
  • /aidd-dev:06-test
  • /aidd-dev:08-debug
  • /aidd-vcs:01-commit
Changes

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.

  1. today First seen · 35 lines · 34 tokens per session scan A afe50a56bafd

Subscribe to this mod's changes

executor is an agent published in the GitHub repository ai-driven-dev/framework (453 stars, last pushed today), licensed MIT. It adds 34 tokens to every session and 423 once invoked, about $0.0002 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.

Related

Other agents, from other repositories