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 Owl-Listener/inclusive-design-skills --skill specifygit clone --depth 1 https://github.com/Owl-Listener/inclusive-design-skillsWrote 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/owl-listener/inclusive-design-skills/specify)<a href="https://agentmods.dev/skills/owl-listener/inclusive-design-skills/specify"><img src="https://agentmods.dev/badge/skills/owl-listener/inclusive-design-skills/specify/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/owl-listener/inclusive-design-skills/specify"><img src="https://agentmods.dev/badge/skills/owl-listener/inclusive-design-skills/specify.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.00056 | $0.00483 |
| Opus 5 | $0.00028 | $0.00242 |
| Sonnet 5 | $0.00011 | $0.00097 |
| Haiku 4.5 | $0.00006 | $0.00048 |
Grade A, and why
specify 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 12d 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
Specify Adaptive Behaviour
Define how an interface adapts to diverse user needs — preferences, screen conditions, and cognitive requirements — as part of the design specification, not as a retrofit.
Process
Step 1: Define Preference Responses
Using user-preference-respect, specify how the interface responds to each system preference:
- prefers-reduced-motion: what changes
- prefers-contrast: what changes
- prefers-color-scheme: what changes
- forced-colors: what changes
- prefers-reduced-transparency: what changes
Step 2: Define Responsive Behaviour
Using responsive-accessibility, specify:
- Breakpoints and what reflows at each
- Behaviour at 200% zoom
- Orientation support
- Touch target sizing at each breakpoint
Step 3: Define Typography Behaviour
Using flexible-typography, specify:
- Type scale with relative units
- Line height and spacing values
- Behaviour when user scales text to 200%
- Dark mode typography adjustments
Step 4: Define Colour Strategy
Using colour-independence, specify:
- How every colour-encoded meaning has a second encoding
- Status indicator design (colour + icon + text)
- Chart and data visualisation colour strategy
- Greyscale test results
Step 5: Define View Options
Using simplified-views and information-density, specify:
- What simplified view contains vs full view
- How users toggle between views
- Available density levels
- Default density per viewport and context
Output
Deliver an adaptive behaviour specification:
- Preference response table — each system preference and the interface's response
- Responsive behaviour map — what changes at each breakpoint and zoom level
- Typography specification — scale, units, spacing, scaling behaviour
- Colour independence audit — every colour-dependent element and its second encoding
- View and density options — what's available and how users control it
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.
- 12d ago First seen · 64 lines · 56 tokens per session scan A f2e5e52e8e2c
specify is a skill published in the GitHub repository Owl-Listener/inclusive-design-skills (98 stars, last pushed 3mo ago), licensed MIT. It adds 56 tokens to every session and 483 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-30.
Other skills, from other repositories
chakra-ui-builder
Build responsive, accessible UI components and layouts using Chakra UI v3, install or configure Chakra UI in new and existing projects, and design scalable themes using tokens, semantic tokens, recipes, and slot recipes. Use this skill whenever a user asks to build, create, or generate any UI component, page, form…
visual-ralph
Visual Ralph orchestration for frontend UI from generated references, static references, or live URL targets, using $ultragoal with built-in visual verdict and pixel-diff evidence until the implementation matches and leaves a reproducible design system.
frontend-visual-qa
Audits already-rendered web, landing-page, HTML deck/slide, browser tool/game, dashboard/admin, design-system, and desktop UIs using real-browser or native-app journeys, inspected screenshots, DOM geometry, responsive or projection viewports, and a bundled Playwright sweep. Use after UI implementation to find…
prototype-web
A clickable, high-fidelity web product prototype with navigation, a hero section, feature cards, steps, social proof, and optional pricing. It is designed to resemble a finished landing page while remaining a prototype.
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.
refactoring-ui
Audit and fix visual hierarchy, spacing, color, and depth in web UIs. Use when the user mentions "my UI looks off" (or amateur/unprofessional), "fix the design", "Tailwind styling", "color palette", "visual hierarchy", "design system", "spacing scale", or "component styling". Also trigger when building consistent…