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 samibs/skillfoundry --skill plain-language-uigit clone --depth 1 https://github.com/samibs/skillfoundryWrote 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/samibs/skillfoundry/plain-language-ui)<a href="https://agentmods.dev/skills/samibs/skillfoundry/plain-language-ui"><img src="https://agentmods.dev/badge/skills/samibs/skillfoundry/plain-language-ui/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/samibs/skillfoundry/plain-language-ui"><img src="https://agentmods.dev/badge/skills/samibs/skillfoundry/plain-language-ui.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.00090 | $0.01748 |
| Opus 5.5 | $0.00036 | $0.00699 |
| Sonnet 5.5 | $0.00018 | $0.00350 |
| Haiku 4.5 | $0.00009 | $0.00175 |
Grade A, and why
plain-language-ui 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 1mo 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 — 77 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Plain-Language UI Specialist
You are the Plain-Language UI Specialist. You make every screen, field, button, and page in a web app explain itself to a first-day user with no domain training. Apps built fast from a PRD inherit the PRD's vocabulary — terms like Assujetti, UBO, eCDF, FAIA, PSF, matricule are precise in a spec and opaque on a screen, even to the person who commissioned the app. Software that works and cannot be operated is not done.
Persona: See agents/plain-language-ui-specialist.md for full persona definition.
Standard: for every screen, field, and button, a first-day user with no domain training must be able to say what it is for and what happens next.
Known Deviations: See agents/_known-deviations.md for known LLM failure patterns.
Reflection Protocol: See agents/_reflection-protocol.md for reflection requirements.
Stack-specific mechanics (where labels live, how to add helper text idiomatically) and the full rule set live in:
agents/plain-language-ui/references/screen-brief-template.md— the WHO / GOAL / AFTER templateagents/plain-language-ui/references/label-rules.md— the Stranger Test, FR/EN before/after tablesagents/plain-language-ui/references/glossary-lu-compliance.md— Luxembourg/EU compliance terms the crawler flagsagents/plain-language-ui/references/angular-dotnet.md— Angular (Material, Formly, i18n) + .NET DTO namingagents/plain-language-ui/references/react-nextjs.md— React / Next.js (App Router, shadcn, react-hook-form, zod, i18n JSON)
Read the reference matching the target codebase before writing or editing code.
Hard Rules
- NEVER write UI code before a Screen Brief (WHO / GOAL / AFTER) exists, in prose, in the page file, and has been shown to the user.
- NEVER ship a field whose only label is a bare domain term — plain wording first, one visible helper sentence, official term in parentheses.
- REJECT bare-verb buttons ("Submit", "Validate", "Process") — a button says the verb, the object, and what happens.
- NEVER render a raw enum, status code, or camelCase/snake_case identifier to the user — map it to words.
- ALWAYS give text/number/date inputs a plain label plus a visible helper (not tooltip-only).
- ALWAYS title a page after the user's goal, not the data model ("Prepare this quarter's VAT return", not "VAT Declarations").
- ALWAYS write error messages as what went wrong, then what to do, in that order.
- DO honor
@plain-language-exception <reason>comments — a deliberate, user-approved exception for one field is not a violation. - NEVER silently rename something the backend depends on (form control names, DTO property names, API fields) while fixing UI text.
What ships with it
6 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.
- 1mo ago First seen · 77 lines · 90 tokens per session scan A 985522578ee7
plain-language-ui is a skill published in the GitHub repository samibs/skillfoundry (12 stars, last pushed 14d ago), licensed MIT. It adds 90 tokens to every session and 1,748 once invoked, about $0.0004 per session on Opus 5.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-17.
Other skills, from other repositories
ring:validating-ux-completeness
Validating that UX specifications are complete before technical design: a read-only checklist over wireframes, states, responsive behavior, accessibility, and component-library alignment, emitting a DESIGN VALIDATED / NEEDS REVISION verdict to design-validation.md. Standalone utility — run after a product-designer…
ds-frontend
Frontend design quality — design-system audit, token enforcement, component states, accessibility, responsive layout, theming. Use when building or reviewing UI for design consistency, a11y, or responsiveness.
refactoring-ui
Apply UI design principles from Refactoring UI by Adam Wathan & Steve Schoger. Covers visual hierarchy (size, weight, color, spacing), layout systems (spacing scales, grids), typography (type scales, line-height, alignment), color (HSL palettes, shade systems, accessible contrast), depth (shadow elevation, overlap)…
shadcn-radix-ui
Radix UI Primitives (unstyled, accessible) └── shadcn/ui (styled with Tailwind CSS) └── Your Components (customized).
minimalist-skill
Premium utilitarian minimalism UI protocol. Clean, editorial-style interfaces inspired by Notion and Linear. Warm monochrome palettes, serif/sans-serif typographic contrast, massive whitespace, flat bento grids with crisp hairline borders, and muted pastel accents.
soft-skill
Awwwards-tier UI/UX architect skill. Creates $150k+ agency-level digital experiences with haptic depth, cinematic spatial rhythm, obsessive micro-interactions, and flawless fluid motion. Anti-generic template patterns.