Borrowing it
Nothing to install: this file belongs to Everyone-Needs-A-Copilot/claude-copilot. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Everyone-Needs-A-Copilot/claude-copilot/main/.claude/agents/uid.mdgit 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/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/everyone-needs-a-copilot/claude-copilot/uid"><img src="https://agentmods.dev/badge/agents/everyone-needs-a-copilot/claude-copilot/uid.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.00029 | $0.01948 |
| Opus 5.5 | $0.00012 | $0.00779 |
| Sonnet 5.5 | $0.00006 | $0.00390 |
| Haiku 4.5 | $0.00003 | $0.00195 |
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 6d 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.
This is a copy
86% identical to doc — 121 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 — 148 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.
Read/apply .claude/agents/_shared/work-lifecycle.md once per task.
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.
- 6d ago Changed dfd3531440e5
- 7d ago Changed · +2 lines 4f4ddd368059
- 1mo ago Changed · -4 lines 1e5a06de793d
- 1mo ago Changed · +12 lines afb4d97e7944
- 1mo ago 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 (14 stars, last pushed yesterday), licensed MIT. It adds 29 tokens to every session and 1,948 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 86% identical to doc, differing in 121 lines, and is treated as a copy.
Other agents, from other repositories
a11y-architect
Accessibility Architect specializing in WCAG 2.2 compliance for Web and Native platforms. Use PROACTIVELY when designing UI components, establishing design systems, or auditing code for inclusive user experiences.
design-master
Use this agent proactively when a UI needs design judgment: a layout feels cluttered or flat, the hierarchy is unclear, type or color choices need a rationale, or a new component should follow proven principles. It diagnoses the problem against design principles, the masters, and historical movements, then proposes…
vibe-prototype-worker
Prototype guidance and operational publisher for an owned vibe mockup. Read-only advice goes to the same persistent implementation writer; share mode only validates/publishes its reviewed committed result. Never builds, iterates or fixes source in another context.
motion-designer
Expert motion designer for UI animations, micro-interactions, and motion systems.
tone
Design token engineering — token architecture, theming systems, style-dictionary pipelines.
Architekt wnetrz aplikacji
Designer to agent implementacji wizualnej w warstwie BUILD. Otrzymuje raporty Researcher UX i przeksztalca je w działający CSS, design tokeny, palety kolorów, typografie i animacje. Jest mostem między inspiracja wizualna a kodem produkcyjnym.