Borrowing it
Nothing to install: this file belongs to tiagosilva07/zyrax-guard. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/tiagosilva07/zyrax-guard/main/.agents/skills/accessible-components/SKILL.mdgit clone --depth 1 https://github.com/tiagosilva07/zyrax-guardWrote 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/tiagosilva07/zyrax-guard/accessible-components)<a href="https://agentmods.dev/skills/tiagosilva07/zyrax-guard/accessible-components"><img src="https://agentmods.dev/badge/skills/tiagosilva07/zyrax-guard/accessible-components/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/tiagosilva07/zyrax-guard/accessible-components"><img src="https://agentmods.dev/badge/skills/tiagosilva07/zyrax-guard/accessible-components.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.00066 | $0.00709 |
| Opus 5 | $0.00033 | $0.00354 |
| Sonnet 5 | $0.00013 | $0.00142 |
| Haiku 4.5 | $0.00007 | $0.00071 |
Grade A, and why
accessible-components 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 9d 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 — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Production-grade React components
A component is "done" when it handles the messy real world, not just the happy path.
Every component must handle all four states
Never build only the success state. Explicitly handle:
- Loading — show a skeleton or spinner; don't leave a blank flash.
- Empty — a real "nothing here yet" state with guidance, not an empty
<div>. - Error — a recoverable message; never a silent failure or a crash.
- Success — the actual content.
If a component fetches data, all four are required. Reviewers should reject any that only renders the success case.
Accessibility (non-negotiable, build it in from the start)
- Semantic HTML first. A
<button>is a button. Don't make<div onClick>when a native element exists — you lose keyboard and screen-reader support for free. - Keyboard operable. Everything clickable must be reachable and usable with Tab /
Enter / Space / Esc. Visible focus styles — never
outline: nonewith no replacement. - Labels & names. Every input has an associated
<label>. Icon-only buttons get anaria-label. Images get meaningfulalt. - ARIA only when HTML can't. Prefer native semantics; reach for ARIA roles/states for custom widgets (modals, tabs, comboboxes) and manage focus correctly.
- Color isn't the only signal. Pair color with text/icon; check contrast (WCAG AA).
- Announce dynamic changes (loading, errors) via
aria-livewhere appropriate.
Reusability & API design
- Props are a contract. Type them precisely; required vs optional is meaningful. Provide sensible defaults so the common case is one line.
- Composition over configuration. Prefer
childrenand slots over a dozen boolean flags. If a component has 15 props, it's probably two components. - Controlled vs uncontrolled — pick one deliberately and document it.
- Don't hardcode spacing/colors; use design tokens / theme variables.
- No business logic inside presentational components — pass data and callbacks in.
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.
- 9d ago First seen · 69 lines · 66 tokens per session scan A 638cdea58d4a
accessible-components is a skill published in the GitHub repository tiagosilva07/zyrax-guard (2 stars, last pushed 28d ago), licensed MIT. It adds 66 tokens to every session and 709 once invoked, about $0.0003 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-31.
Other skills, from other repositories
skillshare-ui-website-style
Skillshare frontend design system for the React dashboard (ui/) and Docusaurus website (website/). Use this skill whenever you: build or modify a dashboard page or component in ui/src/, style or layout website pages or custom CSS in website/, create new React components for the dashboard, add pages to the dashboard…
antd
Use when the user's task involves Ant Design (antd) — writing antd components, debugging antd issues, querying antd APIs/props/tokens/demos, migrating between antd versions, or analyzing antd usage in a project. Triggers on antd-related code, imports from 'antd', or explicit antd questions.
igniteui-blazor-generate-from-image-design
Implement Blazor application views from design images using Ignite UI Blazor components. Uses MCP servers (igniteui-cli, igniteui-theming) to discover components, generate themes, and follow best practices. Triggers when the user provides a design image (screenshot, mockup, wireframe) and wants it built as a working…
igniteui-wc-generate-from-image-design
Implement application views from design images using Ignite UI Web Components. Uses MCP servers (igniteui-cli, igniteui-theming) to discover components, generate themes, and follow best practices. Triggers when the user provides a design image (screenshot, mockup, wireframe) and wants it built as a working view with…
igniteui-angular-generate-from-image-design
Implement Angular application views from design images using Ignite UI Angular components. Uses MCP servers (igniteui-cli, igniteui-theming, angular-cli) to discover components, generate themes, and follow best practices. Triggers when the user provides a design image (screenshot, mockup, wireframe) and wants it built…
motion-lexicon
Design, build, compose, implement, review, and contribute polished product interfaces with Motion Lexicon components and motion primitives. Use this skill when a user asks for a complete React page, landing page, dashboard, settings screen, or product surface in the Motion Lexicon visual language; asks what motion…