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 rewritegit 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/rewrite)<a href="https://agentmods.dev/skills/owl-listener/inclusive-design-skills/rewrite"><img src="https://agentmods.dev/badge/skills/owl-listener/inclusive-design-skills/rewrite/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/rewrite"><img src="https://agentmods.dev/badge/skills/owl-listener/inclusive-design-skills/rewrite.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.00039 | $0.00429 |
| Opus 5 | $0.00019 | $0.00215 |
| Sonnet 5 | $0.00008 | $0.00086 |
| Haiku 4.5 | $0.00004 | $0.00043 |
Grade A, and why
rewrite 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.
What it actually says
Rewrite for Accessibility
Take existing content and rewrite it to be accessible to people with diverse cognitive abilities and literacy levels — without losing accuracy or meaning.
Process
Step 1: Assess Current Readability
Using readable-content, evaluate:
- Current reading level
- Sentence and paragraph length
- Jargon and specialist terms
- Content structure and scannability
Step 2: Identify the Core Message
For each section, answer: what is the one thing the reader must understand? Write that down in one plain sentence. This becomes the opening line of the rewritten section.
Step 3: Rewrite
- Replace jargon with plain alternatives
- Shorten sentences to 15–20 words
- One idea per sentence, one topic per paragraph
- Front-load each paragraph with the key point
- Use active voice throughout
- Address the reader as "you"
- Add examples to clarify abstract concepts
Step 4: Fix Links
Using link-text-design, rewrite any link text that doesn't make sense on its own. Replace "click here" and "read more" with descriptive link text.
Step 5: Present Before and After
Show the original alongside the rewrite with annotations explaining each change. Include the reading level of both versions.
Rules
- Never sacrifice accuracy for simplicity — if a term is essential, keep it and define it
- Don't condescend — plain language is clear language, not childish language
- Preserve the author's intent and tone where possible
- Flag any content where simplification might change the legal or technical meaning — let the team decide those tradeoffs
Output
Deliver the rewritten content with:
- Reading level of original vs. rewrite
- Change log of significant edits with rationale
- Flagged passages where meaning may have shifted
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 · 60 lines · 39 tokens per session scan A 72a145d15ed6
rewrite is a skill published in the GitHub repository Owl-Listener/inclusive-design-skills (98 stars, last pushed 3mo ago), licensed MIT. It adds 39 tokens to every session and 429 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…