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 skills/everyone-needs-a-copilot/claude-copilot/uidsnpx skills add Everyone-Needs-A-Copilot/claude-copilot --skill uidsgit 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/skills/everyone-needs-a-copilot/claude-copilot/uids)<a href="https://agentmods.dev/skills/everyone-needs-a-copilot/claude-copilot/uids"><img src="https://agentmods.dev/badge/skills/everyone-needs-a-copilot/claude-copilot/uids.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.1 | $0.00040 | $0.01023 |
| Opus 5 | $0.00020 | $0.00511 |
| Sonnet 5 | $0.00008 | $0.00205 |
| Haiku 4.5 | $0.00004 | $0.00102 |
Grade A, and why
uids 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 yesterday.
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 — 80 lines — stays where its author put it; the contents beside it link to each section on GitHub.
UI Designer
Use this skill to define the visual system and interface hierarchy.
Operating Lens
- Choose a specific aesthetic direction, not a generic mood.
- Make hierarchy express information architecture.
- Use restrained, accessible palettes and stable component geometry.
- Keep product language scannable, tonally consistent, and visually matched to component hierarchy.
- Design reusable tokens when the surface will recur.
- Treat every state as part of the design, not an implementation afterthought.
Workflow
-
Read
08-taste/INDEX.mdfrom the nearestpaths.knowledge_repoentry that has one — resolved tensions from this owner's own feedback, personal tier only, empty until earned. Apply the reasoning, not the example; when a rule does not fit, say so rather than forcing it. -
Read the product context and existing UI conventions.
-
Pick the visual direction and explain the rationale.
-
Define hierarchy, spacing, type scale, color roles, component treatment, and product-language presentation.
-
Specify responsive behavior and state styling.
-
Identify what
$uidneeds to implement faithfully.
Success Criteria
- Visual hierarchy matches information priority.
- Color, type, spacing, and component rules are specific.
- Product language presentation is scannable and accessible.
- Responsive and state styling expectations are defined.
- A
specificationwork product is stored whentccontext exists.
Iteration Loop
Iterate until the visual direction is specific enough for $uid to implement without inventing core style decisions.
Methodology
Use design-system thinking, Rams-style reduction, and accessible contrast as constraints.
Anti-Generic Rules
- Do not use one-note palettes or decorative effects as the whole design.
- Do not leave component states to implementation guesswork.
- Do not let visual styling obscure task clarity.
HTML Walkthrough Deliverable (Required)
Every design engagement ships two artifacts: the markdown specification and a clickable HTML walkthrough — a single self-contained file that steps through the designed flow screen by screen, so the owner sees and feels the process before any code is written.
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.
- yesterday First seen · 80 lines · 40 tokens per session scan A cd8a27c2958b
uids is a skill published in the GitHub repository Everyone-Needs-A-Copilot/claude-copilot (13 stars, last pushed yesterday), licensed MIT. It adds 40 tokens to every session and 1,023 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-09-04.
Other skills, from other repositories
cadence-first
Meta-orchestrator: assigns skill-chain cadence per block (Tier 1/2/3) via Q1-Q6 rules. Reads target taskblocks + task.md, writes cadence-decisions-{R}.md artifact. Standalone (executor invokes) or Batch (generator hand-off). Use when: deciding cadence for a batch of blocks, generator hand-off from decomposition skills.
ship-first
Final task completion protocol: report → user-note → deploy → smoke test → close? → guide? → routing.db → propagate → STATUS → sessions. Invoked from fast-track and pipeline flows after task execution, not directly by the user. Use when: invoked after the execute step of a fast-track or pipeline task.
ui-ai-first
Final audit of a large task before closure — finds which operations are available only via code / curl / SQL and decides per each: automate with a skill or AI agent (A) or create a UI task (B). Protects against invisible usability debt. Walks through each implemented block: reads task.md + reports + guides + code →…
decision-first
Makes an architectural / project / scope decision using a 5-part model INSTEAD of asking the user. Structure: 🎯 Decision / Why / 🛡 Security / 📈 Scalability / Alternatives / Plain-language analogy. 1 question = 1 atomic artifact. Use when: the agent is about to ask an architectural / scope question…
library-first
Mandatory protocol before executing any fast-track task. Analyzes the task, builds a table: what we do / where it comes from / how many lines of code. Principle: maximum reuse of existing libraries and components, minimum new code. Waits for explicit user approval — does nothing until confirmed. Use when: fast-track…
fixture-new
Creates a parity fixture — the frozen scenario plus the contract its output must satisfy. Asks which skill and case, what shape the run must produce, and writes input.md and expect.yml. Ends by proving the new fixture actually fails on an empty directory. A fixture that passes when nothing ran is worse than no…