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 glebis/humane-agentic-design --skill ux-writinggit clone --depth 1 https://github.com/glebis/humane-agentic-designWrote 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/glebis/humane-agentic-design/ux-writing)<a href="https://agentmods.dev/skills/glebis/humane-agentic-design/ux-writing"><img src="https://agentmods.dev/badge/skills/glebis/humane-agentic-design/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/glebis/humane-agentic-design/ux-writing"><img src="https://agentmods.dev/badge/skills/glebis/humane-agentic-design/ux-writing.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00162 | $0.03323 |
| Opus 5 | $0.00081 | $0.01662 |
| Sonnet 5 | $0.00032 | $0.00665 |
| Haiku 4.5 | $0.00016 | $0.00332 |
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 10d 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 — 276 lines — stays where its author put it; the contents beside it link to each section on GitHub.
UX Writing
Announce at start: "I'm using the humane:ux-writing skill to write and review the words inside this product."
The words are part of the interface, not a layer applied to it. A control that names its exact action needs no tooltip; an error that says what to do next needs no support ticket. Clear beats clever, consistent beats varied, and the best error message is the interaction redesigned so the error cannot happen.
What this skill owns, and what it doesn't
Owns: the source wording of every user-facing string, and the decision about what a string must accomplish.
That includes documentation prose — READMEs, docs pages, release notes,
onboarding guides. The principles below were written for interface strings and
most transfer directly (accuracy, one vocabulary, nothing does double duty, no
selling); where a principle is interface-specific it is marked. A doc that
contradicts the thing it documents is a HIGH finding, not a typo.
| Adjacent concern | Owner |
|---|---|
How copy renders — capitalization via text-transform, truncation, smart punctuation, measure |
layout-rules (and better-typography if interfaces is installed) |
| Whether the layout has room for the translated string | layout-rules |
Error markup and announcement (aria-invalid, live regions) |
nielsen-heuristics for the heuristic; better-accessibility for the implementation |
| Whether the copy lands with strangers | respondent-panel |
| Whether a stakeholder objects to the argument | persona-review |
| Brand voice for marketing surfaces, taglines, transformation claims | brandkit, before-after |
This skill writes the words. It does not judge the usability of the flow around
them — that is nielsen-heuristics.
Quick Reference
| Category | When to use | Reference |
|---|---|---|
| Copy patterns | Ready-made shapes for errors, empty states, confirmations, toggles, notifications | patterns.md |
Step 0 — Read the evidence before writing a word
What ships with it
2 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.
- 10d ago First seen · 276 lines · 162 tokens per session scan A 0ca4d96d70ef
ux-writing is a skill published in the GitHub repository glebis/humane-agentic-design (28 stars, last pushed 8d ago), licensed MIT. It adds 162 tokens to every session and 3,323 once invoked, about $0.0008 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
figma-extract-design-system
Extract a design system from vibe-coded production apps that never had one: inventory components, mine de-facto styling into DTCG tokens, scaffold a Storybook package, port components, and optionally round-trip tokens/components into Figma. Use when the user wants to 'extract a design system', 'create a design system…
figma-version-history
List a Figma file's version history, snapshot the file at any past version, and diff two versions (added/removed/renamed pages plus deep per-component changes). Use when the user wants to inspect Figma history — triggers: 'list Figma versions', 'what versions does this file have', 'show version history', 'snapshot…
figma-blame-node
Find which Figma version introduced a specific change — a component property or a child node — via a binary search over version history (log2(N) API calls instead of N). Answers 'who added this and when'. Use when the user wants git-blame-style attribution for a Figma design — triggers: 'when was this component…
figma-comments
Read, post, reply to, and delete comments on a Figma file via the REST API — including pinning a comment to a specific node and threading replies. Use when the user wants to work with Figma comments programmatically — triggers: 'get Figma comments', 'read comments on this file', 'post a comment in Figma', 'leave a…
figma-export-tokens
Export Figma variables to design token files in DTCG, CSS custom properties, Tailwind v4/v3, SCSS, TypeScript, JSON, Style Dictionary, or Tokens Studio. Use when the user wants to pull design tokens OUT of Figma into code — triggers: 'export tokens', 'export Figma variables', 'generate CSS variables from Figma', 'turn…
figma-generate-component-doc
Generate complete Markdown documentation for a Figma component — anatomy/layer tree, design tokens (colors, spacing, typography), states/variants matrix, accessibility notes, content guidelines, and optional code-parity + YAML frontmatter. Use when the user wants a docs page or handoff spec for a component or…