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/designpowers --skill inclusive-personasgit clone --depth 1 https://github.com/Owl-Listener/designpowersWrote 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/designpowers/inclusive-personas)<a href="https://agentmods.dev/skills/owl-listener/designpowers/inclusive-personas"><img src="https://agentmods.dev/badge/skills/owl-listener/designpowers/inclusive-personas/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/designpowers/inclusive-personas"><img src="https://agentmods.dev/badge/skills/owl-listener/designpowers/inclusive-personas.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00040 | $0.00880 |
| Opus 5 | $0.00020 | $0.00440 |
| Sonnet 5 | $0.00008 | $0.00176 |
| Haiku 4.5 | $0.00004 | $0.00088 |
Grade A, and why
inclusive-personas 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 11d 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 — 99 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Inclusive Personas
Personas shape every design decision that follows. If your personas only represent able-bodied, neurotypical, tech-savvy adults with fast internet, your design will only work for those people. This skill ensures the full range of human experience is represented from the beginning.
The Principle
"Nothing About Us Without Us." Design for the margins and the centre benefits. Design for the centre and the margins get excluded.
Process
Step 1: Map the Ability Spectrum
For the design context, identify the relevant spectrum across:
Permanent conditions:
- Vision: blind, low vision, colour blind
- Hearing: deaf, hard of hearing
- Motor: limited fine motor, limited reach, tremor, paralysis
- Cognitive: learning differences, memory challenges, attention differences
- Speech: non-verbal, speech differences
Temporary conditions:
- Broken arm, ear infection, concussion, medication effects, post-surgery
Situational conditions:
- Bright sunlight, noisy environment, one hand occupied, driving, multitasking, emotional distress, unfamiliar language, slow connection
Step 2: Identify Relevant Personas
Not every project needs every persona. Select 4-6 personas that represent:
- 2-3 primary users — the most common use cases
- 1-2 edge case users — people at the margins whose needs reveal design weaknesses
- 1 stress case user — someone using the design under difficult circumstances
Step 3: Build Each Persona
For each persona, document:
## [Name]
**Context:** [Who they are, what they do, their relationship to this product]
**Abilities and conditions:** [Permanent, temporary, or situational factors that affect how they interact with interfaces]
**Technology:** [Devices, assistive technology, connection speed, technical confidence]
**Goals:** [What they need to accomplish]
**Frustrations:** [What typically goes wrong for them with similar products]
**Environment:** [Where and when they use this — lighting, noise, distractions, time pressure]
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.
- 11d ago First seen · 99 lines · 40 tokens per session scan A a0e28e4f1df0
inclusive-personas is a skill published in the GitHub repository Owl-Listener/designpowers (245 stars, last pushed 2mo ago), licensed MIT. It adds 40 tokens to every session and 880 once invoked, about $0.0002 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
accessibility-a11y
Semantic HTML, keyboard navigation, focus states, ARIA labels, skip links, and WCAG contrast requirements. Use when ensuring accessibility compliance, implementing keyboard navigation, or adding screen reader support.
tailwind-shadcn
Tailwind CSS utility patterns with shadcn/ui component usage, theming via CSS variables, and responsive design. Use when styling components, installing shadcn components, implementing dark mode, or creating consistent design systems.
anti-slop-frontend
A mechanical, countable anti-slop checklist for AI-generated frontend. Catches the specific signatures an undirected model defaults to: AI-purple glows, Inter-everywhere, em-dashes, div-based fake screenshots, eyebrow-on-every-section, beige+brass "premium" palettes, generic Jane Doe / Acme data. Advisory layer that…
frontend-mockup-loop
Plan, build, and iterate UX-friendly frontend mockups via a ground→contract→mockup→test→fix→learn loop, acting as an expert UX designer who grounds every decision in externally documented public design rules (Nielsen heuristics, Laws of UX, WCAG, GOV.UK/USWDS/Material). Uses the bundled servemockup, scoremockup, and…
frontend-mockup-loop-dashboard
Dashboard-specific adapter on the generic frontend-mockup-loop skill: binds the 7-step design loop to pi-agent-dashboard component sources, theme-system tokens, and isolated verification. Use when designing/redesigning any pi-agent-dashboard client surface. Triggers: "design a dashboard screen", "mockup a dashboard…
goga-define-experience
Define the user experience required to achieve the established product goals and solve the identified problem.