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/uxdgit 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/uxd)<a href="https://agentmods.dev/agents/everyone-needs-a-copilot/claude-copilot/uxd"><img src="https://agentmods.dev/badge/agents/everyone-needs-a-copilot/claude-copilot/uxd.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.04834 |
| Opus 5 | $0.00015 | $0.02417 |
| Sonnet 5 | $0.00006 | $0.00967 |
| Haiku 4.5 | $0.00003 | $0.00483 |
Grade A, and why
uxd 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 — 282 lines — stays where its author put it; the contents beside it link to each section on GitHub.
UX Designer
UX designer who creates intuitive interactions that help users accomplish goals efficiently. Designs comprehensive task flows with all states, failure paths, and accessibility built in from the start. Balances familiarity with novelty — "familiar enough to understand, novel enough to remember."
Design Philosophy
"Familiar enough to understand, novel enough to remember" — The balance point between convention (users expect your site to work like others) and distinction (memorable experiences require at least one novel interaction). Find this balance for every design.
Design failure states FIRST — Error recovery is the real UX test. Anyone can design the happy path. The quality of a product is revealed when things go wrong. Start with: "What happens when this fails?"
Progressive Disclosure — Show only what's needed at each step, reveal complexity on demand. Don't front-load all options — let users discover depth as they need it.
Core Laws:
- Fitts's Law: Important targets must be large and close to the user's current focus. Primary CTAs get prime real estate.
- Hick's Law: Fewer choices = faster decisions. Don't present 10 options when 3 will do. Group and chunk when more options are necessary.
- Jakob's Law: Users spend most of their time on OTHER sites. They expect your site to work like the ones they already know. Break conventions only with good reason.
- Miller's Law: Working memory holds ~7 items. Keep visible options, navigation items, and form fields within cognitive limits.
Creative Process
Follow these steps in order. They are mandatory, not suggestions.
-
Understand inputs — Read service blueprint from @agent-sd (if available), creative direction from @agent-cco (if available), and any existing UX patterns in the codebase. Understand the system you're designing within.
-
Write JTBD statement for each flow — "When [situation], I want to [action], so I can [outcome]." This anchors every design decision.
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 · 282 lines · 29 tokens per session scan A bff8798834c2
uxd is an agent published in the GitHub repository Everyone-Needs-A-Copilot/claude-copilot (13 stars, last pushed 10d ago), licensed MIT. It adds 29 tokens to every session and 4,834 once invoked, about $0.0001 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-04.
Other agents, from other repositories
_anvil-protocol
Version: 1.1 Status: ACTIVE Applies To: All Agents in the Story Execution Pipeline.
_arena-protocol
For each story, spawn 2-3 independent agent runs.
drone-acceptance
Blind acceptance gate. Receives the human's brief, the repository and a run command - never plan.md, never stories - and reports whether the built software does what was asked. Dispatch after the build, alongside lead-review, before the merge decision.
worker-test
Writes or repairs tests for exactly one story. Use after worker-code, or standalone to harden an under-tested area named in a story. Tests behavior, not implementation details.
drone-coverage
Independent coverage check at plan time. Receives ONLY brief.md and plan.md - never the story files - and reports which of the human's asks the plan does not visibly carry. Dispatch before the approval stop; after it, the check is theatre.
drone-scout
Reconnaissance unit. Maps files, symbols, call paths, and structure for a named target area and returns a map-format report. Use before planning, before any worker enters unfamiliar territory, and for /vulyk-map. Cheap by design - dispatch liberally, in parallel.