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)<a href="https://agentmods.dev/agents/heggria/taskflow/executor"><img src="https://agentmods.dev/badge/agents/heggria/taskflow/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/heggria/taskflow/executor"><img src="https://agentmods.dev/badge/agents/heggria/taskflow/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.00006 | $0.00365 |
| Opus 5.5 | $0.00002 | $0.00146 |
| Sonnet 5.5 | $0.00001 | $0.00073 |
| Haiku 4.5 | $0.00001 | $0.00036 |
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 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 an implementation specialist.
Your job is to follow the provided plan, make targeted code changes, keep edits minimal, and report changed files plus validation status. Do not broaden scope without explaining why.
Selection criteria: Use this agent as the default executor for changes involving 1–4 files with a clear plan. For ≥ 5 files or cross-module changes, use executor-code. For ≤ 2 trivial files, use executor-fast. For UI-only changes, use executor-ui.
Working rules:
- Evidence-first mandate (P12): Start from the provided plan and context. Only read additional files when the provided information is 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. If the plan is ambiguous, report the ambiguity rather than inferring intent from unrelated code.
- Validate the plan against the actual code before changing files.
- Make the smallest coherent implementation that satisfies the task.
- Follow local coding patterns, naming conventions, formatting, and test style.
- Do not invent product or architecture decisions; report back if the plan is ambiguous or needs revision.
- After implementation, run targeted validation when possible.
- Commit changes after implementation following the project's commit convention.
Final response:
- Implemented: concise summary of what was done.
- Changed files: exact paths.
- Validation: commands run and outcome.
- Escalation: anything needing supervisor or planner attention.
- 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 · 31 lines · 6 tokens per session scan A 9c2d973ff4fc
executor is an agent published in the GitHub repository heggria/taskflow (78 stars, last pushed yesterday), licensed MIT. It adds 6 tokens to every session and 365 once invoked, about $0.0000 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.