AminBlg/SimpleEnglish is an agent skill that guides language models to write technical documents in ASD-STE100 Simplified Technical English, a controlled form of plain English used for unambiguous instructions. It is for technical writers and people who want an agent to produce clearer, more readable documentation. The catalogue entries are its skill, plugin, and hook for applying these writing rules in compatible agents.
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 AminBlg/SimpleEnglish --skill simple-englishgit clone --depth 1 https://github.com/AminBlg/SimpleEnglishWrote 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/aminblg/simpleenglish/simple-english)<a href="https://agentmods.dev/skills/aminblg/simpleenglish/simple-english"><img src="https://agentmods.dev/badge/skills/aminblg/simpleenglish/simple-english/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/aminblg/simpleenglish/simple-english"><img src="https://agentmods.dev/badge/skills/aminblg/simpleenglish/simple-english.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket pass
- Snyk pass
- 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.00215 | $0.01822 |
| Opus 5 | $0.00108 | $0.00911 |
| Sonnet 5 | $0.00043 | $0.00364 |
| Haiku 4.5 | $0.00021 | $0.00182 |
Grade A, and why
simple-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 2d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- simple-english — 100% identical, 297 lines differ
How it starts
The opening of the file, as written. The whole thing — 96 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Simple English
Write plain English that a smart reader outside your field understands on one read. The rules come from ASD-STE100, the controlled language aerospace uses so a tired mechanic cannot misread an instruction. Two registers exist: the document you write or rewrite, and the reply you type in chat. Each has its own short rule set below. Nothing else in this file is optional.
The Document
When asked to write or rewrite documentation, apply these rules to the prose:
- Classify each passage. Procedural text tells the reader what to do: imperative mood, 20 words per sentence, one instruction per sentence. Descriptive text explains: simple tenses, 25 words per sentence, one topic per paragraph, six sentences per paragraph at most.
- Never touch code, identifiers, commands, flags, file paths, quoted errors, product names, or facts. When the source gives no number or cause, keep the general statement.
- Condition before command, with a comma. "If the build fails, read the log."
- Simple tenses, active voice. No present perfect ("has completed" → "completed"). No "-ing" verb after a comma (", making it easy" → new sentence). Name the actor: "You run the migration."
- Modals: can, will, must. Never should, would, may, might, could. A required "should" becomes "must". An optional one is deleted.
- Complete grammar. No contractions, keep articles, keep "that". Short sentences, not telegraph style.
- No semicolons and no em-dashes. Write two sentences, or name the relation.
- One word, one meaning, for the whole document. Use
make sure thatfor check, verify, confirm, validate, ensure. Useconfigurationfor config, settings, options. Break noun chains over three words with a preposition ("the timeout value for the connection pool"). - Define a concept term at its first use, under ten words, one per sentence. Do not define product names, standard names (Postgres, S3, HTTP), or the tool the document is about.
- State the fact, not its importance. Delete words that carry no fact: simply, seamlessly, robust, powerful, comprehensive, leverage, crucial, "in order to", "it is worth noting". No "not just X, it is Y". No decorative triplets. No "in conclusion".
- Format for the eye, not for decoration. No bold lead-ins, no bold as emphasis, no emoji, no heading over two sentences. A vertical list is for three or more parallel items or steps: colon on the lead-in, uppercase start, one instruction per item.
- Warnings: command or condition first, then the risk. "Do not run this against production. The command deletes rows."
What ships with it
4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 2d ago Changed 756da5b2fa3c
- 5d ago Changed · -1 lines 49e0b038b63f
- 7d ago Changed · -206 lines · +3 tokens per session 7908df2efe6e
- 10d ago Changed · -27 lines · +63 tokens per session 22f0e2cadcdb
- 12d ago First seen · 330 lines · 149 tokens per session scan A 2c65baeada7c
simple-english is a skill published in the GitHub repository AminBlg/SimpleEnglish (3,336 stars, last pushed 4d ago), licensed MIT. It adds 215 tokens to every session and 1,822 once invoked, about $0.0011 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…
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…