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 sho-das/clear-english --skill claudegit clone --depth 1 https://github.com/sho-das/clear-englishWrote 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/sho-das/clear-english/claude)<a href="https://agentmods.dev/skills/sho-das/clear-english/claude"><img src="https://agentmods.dev/badge/skills/sho-das/clear-english/claude/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/sho-das/clear-english/claude"><img src="https://agentmods.dev/badge/skills/sho-das/clear-english/claude.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.00057 | $0.01804 |
| Opus 5 | $0.00028 | $0.00902 |
| Sonnet 5 | $0.00011 | $0.00361 |
| Haiku 4.5 | $0.00006 | $0.00180 |
Grade A, and why
clear-english 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.
How it starts
The opening of the file, as written. The whole thing — 134 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Clear English (reader-first, concrete)
Write so a smart reader whose first language is not English can follow on the first read - no dictionary, no re-reading. This is not baby talk and not vague simplification. Keep every fact exact and as technical as it needs to be; just deliver it in plain, concrete words. Optimize for "understood in one pass," not for sounding expert.
Voice rules (non-negotiable)
- Common word first. Pick the everyday word over the fancy one: use not "utilize", start not "initiate", enough not "sufficient", about not "regarding", so not "hence", but not "however" when either works. If a short common word carries the meaning, use it.
- One idea per sentence. Keep sentences short. If a sentence has two "and"s, or a clause tucked inside another clause, split it into two.
- Define the term, then use it. Never drop jargon cold. First time, name it and say what it is in plain words - "a hook (a small script the tool runs at a set moment)". After that, the plain term is fine.
- Concrete beats abstract. Show a real example or value, not a category. Not "handle edge cases" but "handle an empty list, and a name with an apostrophe". Not "improves performance" but "the page loads in about 1 second instead of 4".
- From the reader's seat. Say what they see and do, not the internal path. "Click Save and the banner reads 'Saved'" beats "the mutation resolves and state updates".
- No idioms, no hype. A non-native reader trips on idioms; hype words carry no information. Cut "piece of cake", "under the hood", "spin up", "nuke it", "seamless", "robust", "powerful", "leverage", "delve", "simply", "just".
- Meaning stays exact. Simpler words, not simpler facts. Do not round away the truth to shorten a sentence. If something is uncertain, say so plainly: "I am not sure yet - I need to check X."
- Spell out an acronym once. First use, expand and gloss it: "PTY (a fake terminal the app controls)". Then "PTY" is fine.
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 · 134 lines · 57 tokens per session scan A 537be75a43cc
clear-english is a skill published in the GitHub repository sho-das/clear-english (2 stars, last pushed 1mo ago), licensed MIT. It adds 57 tokens to every session and 1,804 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
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…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
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…