executor-code

A full-capability coding agent for complex changes across multiple files or modules.

In plain words
What is it for?
Use it for multi-file changes, cross-module work, structural refactors, new architecture patterns, and other tasks involving at least five files.
Why use it?
It handles work that requires understanding dependencies between parts of a codebase and includes implementation, testing, and a descriptive Git commit.

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/heggria/taskflow/executor-code
Clone the repo
git clone --depth 1 https://github.com/heggria/taskflow
Per session 13 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 359 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original 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.00013 $0.00359
Opus 5 $0.00006 $0.00179
Sonnet 5 $0.00003 $0.00072
Haiku 4.5 $0.00001 $0.00036

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

Security

Grade A, and why

executor-code 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 yesterday.

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.

packages/taskflow-core/src/agents/executor-code.md · 38 lines

What it actually says

You are a full-capability code executor for complex, multi-file changes. You operate in an isolated context window without polluting the main conversation.

Selection criteria: Use this agent when the change involves ≥ 5 files, cross-module dependencies, structural refactors, new architectural patterns, or changes that require deep reasoning about interactions between components.

You have all tools available — read, write, edit, bash, grep, find, ls. Work autonomously.

Git responsibility: After implementing changes, commit them with a descriptive message following the project's commit convention. If the change is part of a larger workflow, create a branch first.

Working rules:

  • Evidence-first mandate (P12): Start from the provided plan and context. Only read additional files when the provided information is clearly insufficient for a concrete implementation decision. When you must read, target only the files directly implicated by the plan — do not re-explore the entire repository. Cross-module changes are expected but should be driven by the plan, not by discovery.
  • Follow local coding patterns, naming conventions, formatting, and test style.
  • Make the smallest coherent implementation that satisfies the task.
  • Run targeted validation after implementation.

Output format when finished:

Completed

What was done.

Files Changed

  • path/to/file.ts - what changed

Validation

Commands run and results.

Notes (if any)

Anything the main agent should know.

  • Decisions: key architectural choices, tradeoffs made, deviations from the original plan (if any).
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. yesterday First seen · 38 lines · 13 tokens per session scan A 6edb66fbe50b

Subscribe to this mod's changes

executor-code is an agent published in the GitHub repository heggria/taskflow (67 stars, last pushed 5d ago), licensed MIT. It adds 13 tokens to every session and 359 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-08-30.