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 agentmods add skills/juspay/xyne-spaces/responsive-accessibilitynpx skills add juspay/xyne-spaces --skill responsive-accessibilitygit clone --depth 1 https://github.com/juspay/xyne-spacesWrote 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/juspay/xyne-spaces/responsive-accessibility)<a href="https://agentmods.dev/skills/juspay/xyne-spaces/responsive-accessibility"><img src="https://agentmods.dev/badge/skills/juspay/xyne-spaces/responsive-accessibility.svg" alt="Measured on agentmods" 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.00027 | $0.00233 |
| Opus 5 | $0.00014 | $0.00117 |
| Sonnet 5 | $0.00005 | $0.00047 |
| Haiku 4.5 | $0.00003 | $0.00023 |
Grade A, and why
responsive-accessibility 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 6d 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.
What it actually says
Responsive and accessible UI
Treat mobile and accessibility as design inputs, not cleanup.
- Start from content behavior: allow wrapping, use fluid widths, set sensible max-widths, and avoid fixed heights around text.
- Add breakpoints only where the composition actually fails. Convert multi- column layouts into an intentional stacked order on narrow screens.
- Use semantic headings in order, associated labels, button elements for actions, links for navigation, and helpful alternative text.
- Ensure every interactive element is reachable and usable by keyboard.
- Include visible
:focus-visible, hover, active, disabled, and error states. - Respect
prefers-reduced-motionand do not rely on hover for essential info. - Maintain WCAG AA-style contrast for normal text and important controls.
Validate at approximately 1440px, 1024px, 768px, and 390px widths. Check for horizontal overflow, clipped text, inaccessible menus, and reflow problems.
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.
- 6d ago First seen · 23 lines · 27 tokens per session scan A db300b55b49d
responsive-accessibility is a skill published in the GitHub repository juspay/xyne-spaces (142 stars, last pushed yesterday), licensed Apache-2.0. It adds 27 tokens to every session and 233 once invoked, about $0.0001 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
omh-visual-qa
This is a Hermes-native visual-qa workflow skill.
omh-frontend
This is a Hermes-native frontend workflow skill.
handoff-spec
Write the implementation handoff — measurements, behaviours, assets, states, and edge cases. Use when engineering picks up the work. For verifying the result afterwards use design-qa-checklist; for reusable library components use component-spec (design-systems).
readable-measure
Set line length and measure for comfortable reading across type sizes and breakpoints. Use when tuning body text. Covers measure only — for the full size and weight scale, use typography-scale.
von-restorff-effect
Apply the Von Restorff Effect — the element that differs from its neighbours is the one remembered. Use when a single action must dominate. For overall ordering rather than single-element emphasis, use visual-hierarchy.
animation-principles
Apply animation principles — easing, staging, follow-through — to one specific UI motion. Use when tuning how an animation feels. For product-wide duration and easing tokens use motion-system (design-systems); for a full interaction spec use micro-interaction-spec.