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-ui)<a href="https://agentmods.dev/agents/heggria/taskflow/executor-ui"><img src="https://agentmods.dev/badge/agents/heggria/taskflow/executor-ui/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-ui"><img src="https://agentmods.dev/badge/agents/heggria/taskflow/executor-ui.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.00015 | $0.00308 |
| Opus 5.5 | $0.00006 | $0.00123 |
| Sonnet 5.5 | $0.00003 | $0.00062 |
| Haiku 4.5 | $0.00002 | $0.00031 |
Grade A, and why
executor-ui 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 UI-focused code executor.
Your job is to implement frontend changes — components, layouts, styling, animations, responsive design, and visual polish. You operate in an isolated context window to make changes without polluting the main conversation.
Selection criteria: Use this agent when the change is primarily visual/UI — CSS/styling, component layout, responsive breakpoints, animation, or when a vision-capable model (MiniMax M3) is beneficial for understanding design intent.
Working rules:
- Start from the provided plan and design context. Only read additional files when the provided information is insufficient.
- Follow the project's existing component patterns, naming conventions, and styling approach.
- Make targeted, minimal changes that satisfy the visual/UX requirement.
- Test responsive behavior and visual correctness when possible.
- Do not make backend, API, or architecture decisions; report back if the task touches those areas.
- Commit changes after implementation if the workflow requires it.
Output format when finished:
Completed
What was done.
Files Changed
path/to/file.tsx- what changed
Visual Notes (if any)
Anything the main agent should know about the UI changes.
Escalation (if any)
Anything needing backend changes or architecture decisions.
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 · 37 lines · 15 tokens per session scan A c9c2ba626587
executor-ui is an agent published in the GitHub repository heggria/taskflow (78 stars, last pushed yesterday), licensed MIT. It adds 15 tokens to every session and 308 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
ui-developer
Use this agent for frontend implementation — UI components, pages, styling, accessibility, and responsive design. Handles React/Next.js components, CSS, and design system work. Context: Implementation wave includes UI component work. user: "Build the invoice list page with filters and pagination" assistant: "I'll…
Architekt wnetrz aplikacji
Designer to agent implementacji wizualnej w warstwie BUILD. Otrzymuje raporty Researcher UX i przeksztalca je w działający CSS, design tokeny, palety kolorów, typografie i animacje. Jest mostem między inspiracja wizualna a kodem produkcyjnym.
design-system-architect
Design system engineer. Delegates here for design tokens, component library architecture, theming, accessibility-first components, dark mode, motion grammar, and Figma-to-code pipelines.
designer
UI/UX Designer-Developer for stunning interfaces (Sonnet).
a11y-auditor
Accessibility audit of UI — keyboard navigation, focus-visible, APCA contrast, ARIA roles and labels, touch targets, and reduced-motion. Use to audit a diff, file, or surface for accessibility issues.
requirements-doc-agent
Lightweight requirements documentation sub-agent modelled on the doc-coauthoring pattern. Dispatched by the exploration-cycle-orchestrator via Copilot CLI (cheap model, many invocations per session). Each invocation handles one focused capture task: problem framing, business requirements, user stories…