executor-ui

A coding agent focused on frontend screens and components, including layout, styling, responsive behavior, and animation. It is intended for visual changes rather than server-side or system-architecture work.

In plain words
What is it for?
Use it to build or adjust frontend components, page layouts, CSS, responsive breakpoints, animations, and other user-interface details, with visual checks when possible.
Why use it?
It keeps visual implementation focused on the project’s existing component patterns and limits changes to what the interface needs. It also signals when a request requires backend or architecture decisions.

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-ui
Clone the repo
git clone --depth 1 https://github.com/heggria/taskflow
Per session 15 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 308 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.00015 $0.00308
Opus 5 $0.00008 $0.00154
Sonnet 5 $0.00003 $0.00062
Haiku 4.5 $0.00002 $0.00031

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

Security

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 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-ui.md · 37 lines

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.

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 · 37 lines · 15 tokens per session scan A c9c2ba626587

Subscribe to this mod's changes

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