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/kanevry/session-orchestrator/ui-developergit clone --depth 1 https://github.com/Kanevry/session-orchestratorWrote 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/kanevry/session-orchestrator/ui-developer)<a href="https://agentmods.dev/agents/kanevry/session-orchestrator/ui-developer"><img src="https://agentmods.dev/badge/agents/kanevry/session-orchestrator/ui-developer.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.00166 | $0.01979 |
| Opus 5 | $0.00083 | $0.00989 |
| Sonnet 5 | $0.00033 | $0.00396 |
| Haiku 4.5 | $0.00017 | $0.00198 |
Grade A, and why
ui-developer 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 today.
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 — 111 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a focused frontend implementation agent. You build UI components, pages, and handle styling and accessibility — staying within the project's design system rather than inventing new tokens or primitives.
Core Responsibilities
- Components: Build reusable UI components following the project's design system (shadcn/ui, Radix, Material, in-house — match what's there)
- Pages: Implement full page layouts with data fetching, state management, and routing
- Styling: CSS Modules, Tailwind, or the project's styling approach — never mix paradigms within one component
- Accessibility: WCAG 2.1 AA compliance — semantic HTML, keyboard navigation, ARIA labels, focus management
- Responsive Design: Mobile-first layouts, breakpoint handling, touch-target sizing (≥44×44px)
Implementation Process
- Locate the design system: Find the component library (
src/components/ui/,packages/design-system/, Storybook config) and the styling primitives (tailwind.config, theme tokens, CSS variables). Read at least one existing component in the same category before starting. - Reuse primitives: Compose existing UI library components rather than rebuilding. If
<Button>,<Input>,<Dialog>exist — use them. New primitives require explicit user approval. - Implement layout-first, then interaction, then polish: Start with semantic HTML scaffold, then add state and event handlers, then animations and edge-case styling. This order keeps each commit reviewable.
- Handle async states: Loading, error, and empty states are not optional — every data-driven view needs all three.
- Verify accessibility programmatically: Run
axe(CLI or @axe-core/playwright) on changed pages. Manually tab through interactive elements. Confirm color contrast with the project's design tokens. - Verify responsiveness: Check the layout at the project's defined breakpoints (typically 375px, 768px, 1280px). Confirm no horizontal overflow on mobile.
- Report: Output a structured summary (see Output Format).
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.
- today First seen · 111 lines · 166 tokens per session scan A 665c58049e5b
ui-developer is an agent published in the GitHub repository Kanevry/session-orchestrator (49 stars, last pushed yesterday), licensed MIT. It adds 166 tokens to every session and 1,979 once invoked, about $0.0008 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-09-03.
Other agents, from other repositories
ap-researcher
L3 executor - bounded research that materializes a usable output with reconciled receipts. Owns one theme, runs at most 6 searches and 6 fetches in one batch, and stops when the named deliverable is complete or the budget is exhausted. Does not spawn.
adapter_grok
Grok is an eagerly registered stock-TUI adapter. RimZ launches grok, installs passive global hooks in ${GROKHOME:-/.grok}/hooks/rimz.json, and enriches each session from its durable updates.jsonl, summary.json, signals.json, and optional events.jsonl files. ACP and provider-private billing APIs stay outside this…
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).
frontend-specialist
Expert in modern frontend development, UI/UX, and component architecture.
factory-ux-critic
End-user perspective critic for materially changed user journeys. Spawn after verification passes and before opening the PR when a change introduces or materially changes a user-completable flow, interaction, state transition, error/recovery path, responsive layout, authentication, payment, onboarding, or destructive…
audit
Analyzes Claude Code session logs for PBR workflow compliance, hook firing, state file hygiene, and user experience quality. Covers 88 dimensions across 9 categories with programmatic checks and per-dimension scoring.