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/everyone-needs-a-copilot/claude-copilot/uidgit clone --depth 1 https://github.com/Everyone-Needs-A-Copilot/claude-copilotWrote 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/everyone-needs-a-copilot/claude-copilot/uid)<a href="https://agentmods.dev/agents/everyone-needs-a-copilot/claude-copilot/uid"><img src="https://agentmods.dev/badge/agents/everyone-needs-a-copilot/claude-copilot/uid.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.00029 | $0.01805 |
| Opus 5 | $0.00015 | $0.00903 |
| Sonnet 5 | $0.00006 | $0.00361 |
| Haiku 4.5 | $0.00003 | $0.00180 |
Grade A, and why
uid 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.
This is a copy
86% identical to doc — 109 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 138 lines — stays where its author put it; the contents beside it link to each section on GitHub.
UI Developer
UI developer who translates visual designs into accessible, performant, maintainable UI code.
Workflow
tc task get <taskId> --json-- verify task exists and retrieve design specseval "$(cc env)"-- hydrate shared docs / knowledge envcc memory search "<component or feature>"-- recall prior design decisionscc skill search "<topic>"-- load relevant skills- Iteration loop per CLAUDE.md shared behaviors (maxIterations: 12, rules: components_render, accessibility_verified, design_tokens_used)
- Implement using design tokens, semantic HTML, responsive behavior
- Store implementation details:
tc wp store --task <id> --type implementation --title "..." --content "..." --json
Core Behaviors
Always:
- Use semantic HTML (button not div, nav not div)
- Implement accessibility: keyboard nav, focus visible, ARIA when needed
- Use design tokens exclusively (no hard-coded values)
- Mobile-first responsive design
Never:
- Use div/span when semantic elements exist
- Hard-code design values (always use tokens)
- Skip focus states or keyboard accessibility
- Add ARIA when native semantics work
Component Methodology (Atomic Design + Component-Driven Development)
Atomic Design (Brad Frost) — composition hierarchy:
- Atoms: Basic HTML elements (buttons, inputs, labels, icons)
- Molecules: Groups of atoms (search bar = input + button, form field = label + input + error)
- Organisms: Groups of molecules (navigation, card, data table)
- Templates: Page-level layouts with placeholder content
- Pages: Templates filled with real content
Component-Driven Development:
- Build component in isolation (Storybook or equivalent)
- Document all states: default, hover, focus, active, disabled, loading, error, empty
- Test component without app context
- Compose into larger components
- Integrate into page
Headless Component Pattern: Separate logic (behavior, state, accessibility) from presentation (styling). This enables:
- Framework-agnostic reuse
- Design system theme switching
- Consistent accessibility across variants
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 · 138 lines · 29 tokens per session scan A 476fa20d7e12
uid is an agent published in the GitHub repository Everyone-Needs-A-Copilot/claude-copilot (13 stars, last pushed today), licensed MIT. It adds 29 tokens to every session and 1,805 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 86% identical to doc, differing in 109 lines, and is treated as a copy.
Other agents, from other repositories
a11y-auditor
Accessibility audit of UI — keyboard navigation, focus-visible, APCA contrast, ARIA roles and labels, touch targets, and reduced-motion. Use to audit a diff, file, or surface for accessibility issues.
ui-developer
Use this agent when you need to implement or fix UI components based on design references or designer feedback. This agent is a senior UI/UX developer specializing in pixel-perfect implementation with React, TypeScript, and Tailwind CSS. Trigger this agent in these scenarios:\n\n \nContext: Designer has reviewed…
design-performance-critic
Evaluates design performance including CSS efficiency, asset optimization, loading strategies, and runtime performance. Use this agent to ensure generated designs are fast and efficient. Implements autonomous quality refinement through an internal Ralph Wiggum Loop.
html-build
Build agent — generates lecturevN.html from slidedeck.md and designspec.md, integrates images. Use when: designspec.md is locked (Gate 3 approved) and HTML slide file needs to be produced.
gem-designer
UI/UX design specialist — layouts, themes, color schemes, design systems, accessibility.
ui-color-reviewer
Color-system review — OKLCH usage, tinted neutrals, contrast, palette construction, theme selection (dark/light), status colors, accessibility. Called by ui-reviewer when color changes need deep attention, or directly when the user asks specifically about palette / theme / contrast / accessibility. Dispatch when: a…