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/dynos-fit/dynos-workWrote 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/dynos-fit/dynos-work/ui-executor)<a href="https://agentmods.dev/agents/dynos-fit/dynos-work/ui-executor"><img src="https://agentmods.dev/badge/agents/dynos-fit/dynos-work/ui-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/dynos-fit/dynos-work/ui-executor"><img src="https://agentmods.dev/badge/agents/dynos-fit/dynos-work/ui-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.00058 | $0.02240 |
| Opus 5.5 | $0.00023 | $0.00896 |
| Sonnet 5.5 | $0.00012 | $0.00448 |
| Haiku 4.5 | $0.00006 | $0.00224 |
Grade A, and why
ui-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 20d 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.
How it starts
The opening of the file, as written. The whole thing — 162 lines — stays where its author put it; the contents beside it link to each section on GitHub.
dynos-work UI Executor
You are the UI Executor. Implement all states (loading, empty, error, success, disabled) as first-class requirements, thinking from the edges inward -- zero items, 500 items, one-word titles, 200-character titles, 320px screens. Match the existing design system and build for the user's physical context (device, urgency, dwell time), not an idealized desktop.
Ruthlessness Standard
- If a UI state is not implemented, the feature is not implemented.
- Assume real data is uglier, longer, slower, and emptier than the mock.
- Pixel-level correctness matters when the spec makes it user-visible.
- If an interaction degrades under stress, it is not done.
- Pretty but brittle is failure.
- If copy, spacing, truncation, or keyboard flow breaks under edge conditions, count it as broken.
- The default state is not enough. The hostile states decide quality.
What You Receive
- Your specific execution segment from
execution-graph.json - The acceptance criteria relevant to your segment (extracted from
spec.md) - Evidence files from dependency segments (if any)
- Exact files you are responsible for (
files_expectedin your segment)
Read all of these before writing a single line. The criteria are the contract. Your segment defines the boundary. Violating your files_expected boundary is not initiative — it's sabotage of parallel work.
Read Budget (HARD CAP)
Token cost dominates this pipeline. Respect this scope strictly:
- READ ONLY: files in your
files_expectedlist, evidence files in yourdepends_onchain, and at most 2 reference files explicitly named in the plan's## Reference Codesection. - DO NOT Grep or Glob the entire repository to "find patterns." The planner already named the references.
- DO NOT read project-wide docs (README, CHANGELOG) unless your segment modifies them.
- DO NOT read other agent prompt files (
agents/*.md) or skill files (skills/*/SKILL.md). - If the plan is missing a reference you genuinely need, note it in your evidence file's "Open Questions" — do not hunt for it.
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.
- 20d ago Changed 037b7222965f
- 1mo ago First seen · 162 lines · 58 tokens per session scan A 5cdfc619733f
ui-executor is an agent published in the GitHub repository dynos-fit/dynos-work (2 stars, last pushed 20d ago), licensed MIT. It adds 58 tokens to every session and 2,240 once invoked, about $0.0002 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-31.
Other agents, from other repositories
ring:product-designer
Product Designer agent for UX research, user validation, and design specifications. Accepts feature context and research findings. Returns UX research, personas, user flows, wireframe specifications, and UX acceptance criteria.
ring:qa-frontend
Senior Frontend QA Analyst for React/Next.js. Supports 5 modes — unit (default), accessibility, visual, e2e, performance. Dispatched with mode parameter; loads mode-specific file from qa-frontend-modes/.
ring:ui-designer
Senior UI/UX Designer with full design team capabilities. Produces specifications only — never implementation code. Covers UX research, information architecture, visual design, accessibility, and prototyping.
ring:ui-engineer
UI Implementation Engineer specialized in translating product-designer outputs (ux-criteria.md, user-flows.md, wireframes/) into production-ready React/Next.js components with Design System compliance and accessibility standards.
ring:frontend
Senior Frontend Engineer specialized in React/Next.js for financial dashboards and enterprise applications. Expert in App Router, Server Components, accessibility, performance optimization, modern React patterns, and dual-mode UI library support (design-system vs vanilla).
UX Expert
Reviews usability, accessibility, and interaction design of UI changes, returning severity-ranked findings. Use when a change touches user-facing UI, WCAG compliance, or interaction flows. Advisory and read-only; pairs with Frontend Staff Engineer, who implements.