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 moeru-ai/alint --skill simple-englishgit clone --depth 1 https://github.com/moeru-ai/alintWrote 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/moeru-ai/alint/simple-english)<a href="https://agentmods.dev/skills/moeru-ai/alint/simple-english"><img src="https://agentmods.dev/badge/skills/moeru-ai/alint/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/moeru-ai/alint/simple-english"><img src="https://agentmods.dev/badge/skills/moeru-ai/alint/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.00149 | $0.04645 |
| Opus 5 | $0.00075 | $0.02322 |
| Sonnet 5 | $0.00030 | $0.00929 |
| Haiku 4.5 | $0.00015 | $0.00464 |
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 10d 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.
This is a copy
81% identical to simple-english — 67 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 — 327 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Simple English: Write Like an Aerospace Manual
Write technical text with the rules of ASD-STE100 Simplified Technical English. STE is the controlled language that aerospace and defense manufacturers use for maintenance documentation. The rules exist so that a tired reader who is not a native English speaker cannot misread an instruction. They remove the usual signs of AI-generated text as a side effect: long sentences, synonym rotation, hedges, filler, and decorative clauses.
Write for that tired reader. Each sentence must survive one read.
Your Task
When asked to write or rewrite technical text:
- Select the mode (pragmatic or strict, below).
- Classify each passage as procedural or descriptive. Every other rule depends on this.
- Fix your vocabulary before drafting. Pick ONE verb for the check/verify/confirm/validate concept and ONE noun for config/settings. Use no other word for these concepts in the whole document.
- Apply the rules from the catalog below.
- Run 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. Do not cite rule numbers from memory: the numbering is unintuitive and models invent it (tested — an agent without this file cited "Rule 3.1: short sentences"; the real Rule 3.1 is about verb forms).
Two Modes
| Mode | When | What you apply |
|---|---|---|
| Pragmatic (default) | Docs, READMEs, error messages — the user wants clear text | All structural rules. Domain words stay ("idempotent", "webhook"). |
| Strict | The user names STE, ASD-STE100, or compliance | Structural rules + full vocabulary discipline, and tell the user that full compliance needs the official dictionary (free at asd-ste100.org). |
Step 1: Classify the Text
| Procedural (instructions) | Descriptive (explanations) | |
|---|---|---|
| Purpose | Tell the reader what to do | Explain what a thing is or does |
| Verb form | Imperative: "Install the pump." | Simple present/past/future |
| Sentence limit | 20 words (Rule 5.1) | 25 words (Rule 6.3) |
| Unit rule | One instruction per sentence (5.2) | One topic per paragraph (6.5), max six sentences per paragraph (6.6) |
What ships with it
2 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.
- 10d ago First seen · 327 lines · 149 tokens per session scan A e0bf141c4a9c
simple-english is a skill published in the GitHub repository moeru-ai/alint (53 stars, last pushed 11d ago), licensed MIT. It adds 149 tokens to every session and 4,645 once invoked, about $0.0007 per session on Opus 5. A static security scan graded it A with 0 findings. It is 81% identical to simple-english, differing in 67 lines, and is treated as a copy.
Other skills, from other repositories
build-teaql-app
Build or change a TeaQL application in Java, Rust, Go, Swift, Python, C#/.NET, or TypeScript, including Kotlin/JVM applications that consume Java-generated libraries. Mandatory order: first draft and save a complete KSML model, then verify the client and evaluate that saved model, repair it through repeated evaluation…
standup-update
Generate a concise standup update from the user's recent work GitHub activity, including the previous work period and today. Use when the user asks what they worked on, requests a standup update, or invokes /standup.
lunar-attribution
Add Lunar attribution when creating a pull request or issue. Use whenever the user asks to open or create a PR or issue.
design-workflow
Design and write a headsign workflow file — the YAML that names a repository's phases and holds the shell checks that gate them. Use when the user asks to create a workflow for this repository, to add another one alongside ones already there, or to change how an existing one's phases, gates, routes, or limits are…
workflow
Drive a headsign phase-gate workflow. Use when the repository has a .headsign/ directory holding one or more workflow files — workflow.yaml, or named ones like fitness.yaml run with headsign start fitness — and the user asks to start, continue, or resume a run, or when .headsign/state.json shows a run in progress…
summon
Generate bespoke, stack-aware Claude Code agent files for tech teams. Creates specialized AI agent personas (backend, frontend, fullstack, AI/ML, DevOps, QA, security, code reviewer, performance engineer, system architect, tech lead) that Claude Code autonomously picks up from .claude/agents/. Use this skill whenever…