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 acolomba/pi-claude-marketplace --skill simple-englishgit clone --depth 1 https://github.com/acolomba/pi-claude-marketplaceWrote 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/acolomba/pi-claude-marketplace/simple-english)<a href="https://agentmods.dev/skills/acolomba/pi-claude-marketplace/simple-english"><img src="https://agentmods.dev/badge/skills/acolomba/pi-claude-marketplace/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/acolomba/pi-claude-marketplace/simple-english"><img src="https://agentmods.dev/badge/skills/acolomba/pi-claude-marketplace/simple-english.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.00212 | $0.05115 |
| Opus 5 | $0.00106 | $0.02558 |
| Sonnet 5 | $0.00042 | $0.01023 |
| Haiku 4.5 | $0.00021 | $0.00511 |
Grade A, and why
simple-english scanned grade A with 1 finding 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 8d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
General recommendations: keep "that" (GR-1), primary verb first and the tool after "with" (GR-2: "Fetch the URL with curl"), clear pronoun referents (GR-3), "this + noun" (GR-4), inclusive language (GR-7). GR-6: "e.g." → This is a copy
100% identical to simple-english — 297 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 303 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Simple English: Plain Words, Aerospace Discipline
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. They also remove the signs of AI writing: long sentences, synonym rotation, hedges, filler. Each sentence must survive one read.
Your Task
When asked to write or rewrite text:
- Select the mode (Plain or Strict, the table that follows). In Strict mode, read
references/strict-vocabulary.mdbefore you draft. - Classify each passage as procedural or descriptive. Every other rule depends on this.
- Fix your vocabulary before you draft. Use
make sure thatfor check/verify/confirm/validate/ensure as verbs, andconfigurationfor config/settings/options. Use no other word for these concepts in the whole document. - Define a technical term at its first use when a reader outside the field needs it: concept words, not product names or the tool the document is about.
- Apply the catalog that follows. For replies and explanations for outsiders, apply the Plain English rules first.
- Do the self-check before you deliver. This step is not optional.
- Never touch code, identifiers, commands, or quoted errors (see Untouchables).
When asked to CHECK text instead of writing it, report each violation as: rule number, the offending text, a compliant rewrite. Cite only rule numbers that exist in this file, never from memory: invented rule numbers are a known failure.
Two Modes
| Mode | When | What you apply |
|---|---|---|
| Plain (default) | The user wants clear text: docs, READMEs, error messages, answers | Every structural rule in the catalog. Domain words stay ("idempotent", "webhook"). Replies and explanations for outsiders also get the Plain English rules. |
| Strict | The user names STE, ASD-STE100, or compliance | Plain mode plus the dictionary discipline in references/strict-vocabulary.md. Document only: the reply to the user stays Plain. |
What ships with it
5 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.
- 8d 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 acolomba/pi-claude-marketplace (23 stars, last pushed 3d ago), licensed MIT. It adds 212 tokens to every session and 5,115 once invoked, about $0.0011 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). It is 100% identical to simple-english, differing in 297 lines, and is treated as a copy.
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…