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 eugenelim/agent-ready-repo --skill ux-writinggit clone --depth 1 https://github.com/eugenelim/agent-ready-repoWrote 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/eugenelim/agent-ready-repo/ux-writing)<a href="https://agentmods.dev/skills/eugenelim/agent-ready-repo/ux-writing"><img src="https://agentmods.dev/badge/skills/eugenelim/agent-ready-repo/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/eugenelim/agent-ready-repo/ux-writing"><img src="https://agentmods.dev/badge/skills/eugenelim/agent-ready-repo/ux-writing.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Prompt Injection · line 36 Hidden instructions were detected in comments or invisible text. These could contain malicious directives. Manual review is recommended.Fix: Audit all comments and invisible characters. Remove any instructions that direct the agent to perform unauthorized actions. Use plain, reviewable content.
- medium Rogue Agent · line 3 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
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.00212 | $0.02781 |
| Opus 5 | $0.00106 | $0.01391 |
| Sonnet 5 | $0.00042 | $0.00556 |
| Haiku 4.5 | $0.00021 | $0.00278 |
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 8d 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.
How it starts
The opening of the file, as written. The whole thing — 114 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: ux-writing
Shape product intent into the words a user reads in the UI. The pack frames,
de-risks, and decomposes intent into shippable features; this skill writes the
copy those features render. The method is three moves: characterize the voice
along a few axes, write each UI state from a blame-free, actionable formula,
and run a content checklist before the copy ships. It is a method, not a word
bank — framework-agnostic, and it never mandates a schema. The voice axes are in
references/voice-axes.md, the per-state formulas in
references/microcopy-formulas.md, the checklist in references/content-checklist.md.
When a per-screen state matrix from experience-design's user-flow is
present, this skill writes copy per screen × state — one copy entry per
screen/state cell in the matrix — and keys every string to the matrix row. The
state set those cells enumerate is the experience-design pack's shared
quality-floor (empty / loading / error / success / partial / disabled, plus
permission/denied when gated); defer to it by-name for which states a screen
owes copy, rather than inventing a state list. When the matrix is absent the
skill is still fully useful: it writes copy for the states you name directly
(detect-and-degrade; no screen flow required).
Design-seat pairing. This skill is the content layer of the design seat; the design methods and screen-flow artifacts live in the
experience-designpack. See theexperience-designpack'suser-flowskill for the per-screen state matrix this skill can consume.
Scope boundary — surface type is the dividing line. For marketing/acquisition copy voice and positioned copy (hero headlines, above-fold narrative, taglines, announcement copy), use the
experience-designpack'scopy-directionskill;ux-writingcovers product UI copy states (error, empty state, button labels, form labels). Onboarding tri-point: onboarding narrative arc and structure →content-design(experience-design pack); onboarding copy voice and register →copy-direction(experience-design pack); onboarding UI-state strings (loading, error, empty) →ux-writing(this skill).
What ships with it
7 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 8d ago First seen · 114 lines · 212 tokens per session scan A 41d4d469a683
ux-writing is a skill published in the GitHub repository eugenelim/agent-ready-repo (21 stars, last pushed today), licensed Apache-2.0. It adds 212 tokens to every session and 2,781 once invoked, about $0.0011 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
moai-domain-svg-infographic
Author editable SVG technical infographics — architecture, flow, comparison, hierarchy — by computing the layout numerically before writing markup, then rendering a 2x PNG via headless Chromium. Carries a CJK-first font stack, a deterministic source lint, and mermaid-vs-SVG selection rules.
moai-design-tools
Design tool integration specialist covering Figma MCP, Pencil renderer, and Pencil-to-code export. Use when fetching design context from Figma, rendering Pencil designs, or exporting to React/Tailwind code.
moai-tool-svg
SVG creation, optimization, and transformation specialist. Use when creating vector graphics, optimizing SVG files with SVGO, implementing icon systems, building data visualizations, or adding SVG animations.
moai-domain-design-dna
Reverse-engineer a reference design — a screenshot, an image set, or a live URL — into a portable Design DNA JSON across three dimensions (measurable tokens, qualitative style, special-rendering effects), then generate a new self-contained artifact from that JSON. Carries the extraction rules (dominance-based colour…
moai-ref-ui-polish
UI polish and interface-completion reference: the small visual details — concentric border radius, optical alignment, shadow-vs-border, motion easing, typography smoothing, tabular numbers, icon stroke weight, hit areas — that separate polished interfaces from generic ones. Agent-extending skill that amplifies…
moai-domain-uiux
UI/UX design systems specialist covering accessibility, icons, theming, design tokens, and user experience patterns. Use when working on design systems, WCAG compliance, ARIA patterns, or dark mode theming.