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 d-o-hub/github-template-ai-agents --skill reader-ui-uxgit clone --depth 1 https://github.com/d-o-hub/github-template-ai-agentsWrote 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/d-o-hub/github-template-ai-agents/reader-ui-ux)<a href="https://agentmods.dev/skills/d-o-hub/github-template-ai-agents/reader-ui-ux"><img src="https://agentmods.dev/badge/skills/d-o-hub/github-template-ai-agents/reader-ui-ux/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/d-o-hub/github-template-ai-agents/reader-ui-ux"><img src="https://agentmods.dev/badge/skills/d-o-hub/github-template-ai-agents/reader-ui-ux.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.00077 | $0.00606 |
| Opus 5.5 | $0.00031 | $0.00242 |
| Sonnet 5.5 | $0.00015 | $0.00121 |
| Haiku 4.5 | $0.00008 | $0.00061 |
Grade A, and why
reader-ui-ux 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 18d 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 — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Reader UI/UX
Purpose: deliver intentional, localized, accessible reader/admin UX.
When to Use
- Modifying reader/admin React screens, layout primitives, or shared UI components.
- Adding localization copy, accessibility improvements, or design polish.
- Building locale switchers, typography controls, or comment/annotation panels.
Workflow
- Define experience -- confirm viewport-specific layout (mobile drawer vs desktop side panels) + theme rules.
- Localization -- add strings to locale catalogs, ensure fallback, surface locale switcher.
- Accessibility -- keyboard focus, ARIA labels, reduced motion, semantic regions.
- State -- use state management selectors, avoid prop drilling, memoize heavy renders.
- Observability -- log key UI actions with trace IDs.
- Testing -- add component tests; E2E coverage for primary flows.
Checklist
- Layout responsive (mobile/tablet/desktop) with deliberate spacing.
- Strings localized and locale header updated.
- Error states use ErrorBoundary + inline alerts.
- Async effects cancel via AbortController; cleanup functions implemented.
- UI interactions include aria-labels + focus traps where applicable.
See Also
avoid-ai-writing— Avoid AI slop in UI/UXcss-render-performance— CSS render performance optimization
Rationalizations
| Rationalization | Reality |
|---|---|
| "Accessibility is a nice-to-have, not a requirement" | Legal compliance (WCAG, ADA, Section 508) and user inclusion make it mandatory. |
| "I'll add localization later after the UI is done" | Retroactive localization is costly; string extraction and fallback logic should be designed upfront. |
| "Prop drilling is simpler than state management" | Prop drilling breaks at scale; memoized selectors prevent unnecessary re-renders and deep coupling. |
Red Flags
- Reader UI built without keyboard navigation support
- Locale strings hardcoded in components instead of catalog
- Missing ErrorBoundary or AbortController cleanup on async effects
What ships with it
3 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.
- 18d ago Changed 30d90badb824
- 1mo ago First seen · 65 lines · 77 tokens per session scan A e495172bb5d9
reader-ui-ux is a skill published in the GitHub repository d-o-hub/github-template-ai-agents (2 stars, last pushed yesterday), licensed MIT. It adds 77 tokens to every session and 606 once invoked, about $0.0003 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-08-31.
Other skills, from other repositories
web-i18n-react-intl
ICU message format internationalization for React — FormattedMessage, useIntl, defineMessages, and the FormatJS extraction workflow. Load when a project imports react-intl.
harden
Improve interface resilience through better error handling, i18n support, text overflow handling, and edge case management. Makes interfaces robust and production-ready. Use when the user asks to harden, make production-ready, handle edge cases, add error states, or fix overflow and i18n issues.
add-localization
Adds or extends multilingual localization in a Power Pages code-site SPA. Use whenever the user asks to translate, localize, internationalize, support multiple languages, add a language selector, add locale routes, repair an i18n setup, or add languages to an existing React, Vue, Angular, or Astro Power Pages site.
extract-source-sample
Given the path to a finished content-goose ad-run folder, extract everything that defines that ad — recipe shot list, VO script, characters, voices, world, atom-skills, master mp4 — and emit a source-sample.json in the exact shape the upload-ad-sample skill writes to the Goose Ads library. Also links every character…
json-ui
CRITICAL: Use for json-ui component rendering and development. Triggers on: json-ui, json render, component catalog, report render, HTML report, I18nString, i18n, bilingual, language switch, dual language, PaperHeader, AuthorList, Abstract, MetricsGrid, Section, Highlight, Zod schema, catalog.ts, cli.ts…
experience-ui-bundle-localize
MUST activate to localize / internationalize a uiBundles//src/ project (React or Angular): extract hardcoded user-facing strings into Custom Labels, wire a runtime i18n library over the Platform SDK backend, add labels for another language, or troubleshoot label rendering across locales. Triggers: user-facing string…