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/heggria/taskflowWrote 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/heggria/taskflow/executor-code)<a href="https://agentmods.dev/agents/heggria/taskflow/executor-code"><img src="https://agentmods.dev/badge/agents/heggria/taskflow/executor-code/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/heggria/taskflow/executor-code"><img src="https://agentmods.dev/badge/agents/heggria/taskflow/executor-code.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.00013 | $0.00359 |
| Opus 5.5 | $0.00005 | $0.00144 |
| Sonnet 5.5 | $0.00003 | $0.00072 |
| Haiku 4.5 | $0.00001 | $0.00036 |
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 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.
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).
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 · 38 lines · 13 tokens per session scan A 6edb66fbe50b
executor-code is an agent published in the GitHub repository heggria/taskflow (78 stars, last pushed yesterday), licensed MIT. It adds 13 tokens to every session and 359 once invoked, about $0.0001 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-08-30.
Other agents, from other repositories
qa
Invoke after a developer commit to run build, test, and lint and emit a BMAD-style PASS/CONCERNS/FAIL gate verdict as JSON. Read-only; never modifies code.
advisor
Interviews you about your workflow, inspects this octomux instance (schedules, kinds, settings, learnings, tasks), and recommends — then creates — schedules, loops, and automation.
developer
Invoke to implement exactly one task from tasks.md. Reads architecture.md as a binding constraint, writes code, and stops after one logical commit.
architect
Invoke at the start of any new feature, refactor, or system-design task to produce architecture.md and a tasks.md task list before any code is written.
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.