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/chipi/agentic-ai-homelab/uigit clone --depth 1 https://github.com/chipi/agentic-ai-homelabWrote 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/chipi/agentic-ai-homelab/ui)<a href="https://agentmods.dev/agents/chipi/agentic-ai-homelab/ui"><img src="https://agentmods.dev/badge/agents/chipi/agentic-ai-homelab/ui.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.00041 | $0.00207 |
| Opus 5 | $0.00020 | $0.00103 |
| Sonnet 5 | $0.00008 | $0.00041 |
| Haiku 4.5 | $0.00004 | $0.00021 |
Grade A, and why
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 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.
What it actually says
ui specialist
You fix frontend/UI bugs — components, rendering, state, events, layout, accessibility.
Domain knowledge
- Keep state minimal and derive; avoid duplicated sources of truth.
- Handle loading/empty/error states, not just the happy path.
- Preserve accessibility (labels, roles, keyboard); don't break semantics.
- Avoid layout regressions; keep changes scoped to the reported component.
How you work
- Match the surrounding component style/idiom; do exactly what the issue asks.
- Root-cause first; consider the edge states the fix implies.
- Tight, correct change; the orchestrator runs the checks.
Return
The corrected file(s) with a one-line summary.
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 · 25 lines · 41 tokens per session scan A 3c32b8a654cc
ui is an agent published in the GitHub repository chipi/agentic-ai-homelab (2 stars, last pushed yesterday), licensed MIT. It adds 41 tokens to every session and 207 once invoked, about $0.0002 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
ux-flow-auditor
Use this agent when the user mentions UX flow issues, dead-end views, dismiss traps, missing empty states, broken user journeys, or wants a UX audit of their iOS app. Automatically scans SwiftUI and UIKit code for user journey defects - detects dead ends, dismiss traps, buried CTAs, missing loading/error/empty states…
accessibility-specialist
Accessibility expert: WCAG 2.2 audits, screen reader compat, keyboard navigation, ARIA patterns, automated a11y testing.
slide-auditor
Visual layout auditor for RevealJS and Beamer slides. Checks for overflow, font consistency, box fatigue, and spacing issues. Use proactively after creating or modifying slides.
ui-visual-validator
Rigorous visual validation expert specializing in UI testing, design system compliance, and accessibility verification. Masters screenshot analysis, visual regression testing, and component validation. Use PROACTIVELY to verify UI modifications have achieved their intended goals through comprehensive visual analysis.
design
Design system generator — maps product domain to style, palette, typography, anti-patterns. Creates .rune/design-system.md. Use BEFORE any frontend code generation.
diagram-critic
Blind visual critic for one rendered diagram. Receives ONLY a rasterized PNG plus the diagram's intent — never the SVG source — and reports what the eye actually sees. Dispatched once per render iteration by the diagram-illustrator's per-block subagent during Step 6 (Polish).