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 skills add ilyasibrahim/claude-agents-coordination --skill ux-writinggit clone --depth 1 https://github.com/ilyasibrahim/claude-agents-coordinationWrote 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/ilyasibrahim/claude-agents-coordination/ux-writing)<a href="https://agentmods.dev/skills/ilyasibrahim/claude-agents-coordination/ux-writing"><img src="https://agentmods.dev/badge/skills/ilyasibrahim/claude-agents-coordination/ux-writing/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/skills/ilyasibrahim/claude-agents-coordination/ux-writing"><img src="https://agentmods.dev/badge/skills/ilyasibrahim/claude-agents-coordination/ux-writing.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.00048 | $0.00498 |
| Opus 5 | $0.00024 | $0.00249 |
| Sonnet 5 | $0.00010 | $0.00100 |
| Haiku 4.5 | $0.00005 | $0.00050 |
Grade A, and why
ux-writing 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 12d 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.
What it actually says
UX Writing (Core)
Voice
- Professional yet Accessible - Technical precision without jargon
- Educational - Explain complex concepts clearly
- Evidence-Based - Data-driven with context
- Progress-Oriented - Focus on forward momentum
Tone by Context
| Context | Tone | Example |
|---|---|---|
| Executive | Strategic, narrative | "ML models require quality data for production performance" |
| Analyst | Precise, data-rich | "Retention: discovery → silver dataset" |
| Error | Calm, solution-focused | "Unable to load metrics. Check connection and refresh." |
| Success | Confirming, brief | "Pipeline completed successfully." |
Microcopy Patterns
Buttons
- Primary: "View Dashboard" (not "Click to View")
- Secondary: "Learn More" (not "Read Documentation")
- Destructive: "Delete Dataset" (not just "Delete")
Errors
Structure: Problem + Solution
- "Unable to connect. Check URL and try again."
- "File exceeds 10MB. Compress or split."
Empty States
Structure: Explanation + Action
- "No datasets yet. Upload your first dataset to get started."
Loading
Be specific: "Loading dashboard..." not "Loading..."
Data Presentation
Numbers
- Use commas: 1,234,567
- One decimal for %: 45.2%
- Context: "1,234 records (+12% from last month)"
Trends
- Positive: "+12.5%" or "↑ 450 records"
- Negative: "-8.2%" or "↓ 120 records"
Accessibility
Alt Text
Describe: "Bar chart showing training data distribution" Not: "Image of chart"
Links
Specific: "View dataset documentation" Not: "Click here"
Preferred Terms
| Use | Avoid |
|---|---|
| Dataset | Data set |
| Pipeline | ETL process |
| Real-time | Realtime |
| Training data | Train data |
Version: 2.0.0
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.
- 12d ago First seen · 87 lines · 48 tokens per session scan A 8964d0468a1a
ux-writing is a skill published in the GitHub repository ilyasibrahim/claude-agents-coordination (83 stars, last pushed 3mo ago), licensed Unlicense. It adds 48 tokens to every session and 498 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-08-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…