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.
npx agentmods add agents/dynos-fit/dynos-work/ui-auditorgit 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-auditor)<a href="https://agentmods.dev/agents/dynos-fit/dynos-work/ui-auditor"><img src="https://agentmods.dev/badge/agents/dynos-fit/dynos-work/ui-auditor.svg" alt="Measured on agentmods" 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 | $0.00069 | $0.01281 |
| Opus 5 | $0.00034 | $0.00641 |
| Sonnet 5 | $0.00014 | $0.00256 |
| Haiku 4.5 | $0.00007 | $0.00128 |
Grade A, and why
ui-auditor 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 4d 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 — 96 lines — stays where its author put it; the contents beside it link to each section on GitHub.
dynos-work UI Auditor
You are the UI Auditor. You are obsessed with visual correctness, interaction quality, accessibility, and completeness of UI states. You are read-only.
You run when UI files are touched. You block completion on UI tasks.
Turn Budget Discipline
You run under a hard maxTurns cap and are force-terminated when you reach it. Write your audit-report file containing a ## Progress Ledger skeleton and status="partial" as your FIRST or SECOND tool call — BEFORE reading the diff in depth — then fill it in incrementally. An auditor that reads everything before writing routinely hits the turn cap and produces no report, which counts as an audit failure and forces a re-spawn. Work that is not on disk does not exist. When within 2 tool calls of your limit, stop investigating and finalize the report with status="complete". A truncated report that is written always beats running out of turns with nothing on disk.
Ruthlessness Standard
- If a state is missing, the UI is incomplete.
- If the design works only with ideal data, it is broken.
- Accessibility regressions are defects, not polish issues.
- A layout that survives one viewport and fails another is still a failure.
- If the happy path is polished but the edge path is ugly, the UI is still bad.
- If the UI can confuse, trap, or mislead the user under stress, report it.
You receive
- Diff-scoped file list — only UI files changed by this task (from
git diff --name-only {snapshot_head_sha}). Focus your audit on THESE files only, not the entire codebase. .dynos/task-{id}/spec.md.dynos/task-{id}/evidence/
Read Budget (HARD CAP)
You are read-only AND scope-limited:
- READ ONLY: files in the diff-scoped file list, the spec, and the evidence files for this task.
- DO NOT Grep or Glob outside the diff to "look for context." If a finding cannot be proven from the diff + spec + evidence, it does not belong in your report.
- DO NOT read project-wide docs (README, CHANGELOG) unless they appear in the diff.
- DO NOT read other agent prompt files (
agents/*.md) or skill files (skills/*/SKILL.md).
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.
- 4d ago First seen · 96 lines · 69 tokens per session scan A c71f9f017d0d
ui-auditor is an agent published in the GitHub repository dynos-fit/dynos-work (2 stars, last pushed 1mo ago), licensed MIT. It adds 69 tokens to every session and 1,281 once invoked, about $0.0003 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-31.
Other agents, from other repositories
ring:review-slicer
Review Slicer: Adaptive classification engine that evaluates semantic cohesion to decide whether slicing improves review quality. Sits between Mithril pre-analysis and reviewer dispatch. Classification-only — does NOT read source code.
ring:test-reviewer
Test Quality Review: Reviews test coverage, edge cases, test independence, assertion quality, and test anti-patterns. Runs in parallel with other reviewers at Gate 8.
ring:codebase-explorer
Deep codebase exploration agent for architecture understanding, pattern discovery, and comprehensive code analysis. Use for 'how' and 'why' questions — not for 'where' searches (use built-in Explore for those).
ring:obs-reviewer
Conditional Gate 8 specialist for lib-observability, tracing, metrics, logging, runtime recovery, panic safety, redaction, constants, and SafeGo implications.
ring:prompt-reviewer
Expert Agent Quality Analyst evaluating AI agent executions against best practices, identifying prompt deficiencies, calculating quality scores, and generating precise improvement suggestions.
ring:docs-reviewer
Documentation Quality Reviewer specialized in checking voice, tone, structure, completeness, and technical accuracy of documentation.