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 dirtybits/agent-skills --skill simplified-technical-englishgit clone --depth 1 https://github.com/dirtybits/agent-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/dirtybits/agent-skills/simplified-technical-english)<a href="https://agentmods.dev/skills/dirtybits/agent-skills/simplified-technical-english"><img src="https://agentmods.dev/badge/skills/dirtybits/agent-skills/simplified-technical-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/dirtybits/agent-skills/simplified-technical-english"><img src="https://agentmods.dev/badge/skills/dirtybits/agent-skills/simplified-technical-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.00100 | $0.01329 |
| Opus 5 | $0.00050 | $0.00665 |
| Sonnet 5 | $0.00020 | $0.00266 |
| Haiku 4.5 | $0.00010 | $0.00133 |
Grade A, and why
simplified-technical-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 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.
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 — 139 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Simplified Technical English
Use clear, controlled technical English. Make each label and instruction understandable without private context. Preserve technical accuracy while reducing ambiguity.
Core Rules
- Name the topic in every label. Make a heading, gate, phase, mode, or status understandable in
isolation.
- Use:
Base Sepolia Gate A — Pre-deployment verification. - Do not use:
Gate A. - Use:
Stripe Checkout Phase 2 — Webhook reconciliation. - Do not use:
Phase 2.
- Use:
- Use one term for one meaning. Select a canonical term and use it consistently. Do not switch
between synonyms such as
report,claim, anddisputeunless they identify different objects. - Use one topic per paragraph. Split mixed requirements, explanations, and exceptions into separate paragraphs or lists.
- Write one action per instruction. Use active voice and name the actor when ownership matters.
- Put the condition before the action. Use:
If verification fails, keep the deployment paused. - Use short wording. Prefer short sentences and familiar words. Remove filler that does not change the requirement.
- Use vertical lists for complex information. Put each condition, action, or result on its own line.
- Explain shorthand at first use. Pair required codes with their topic:
Base Mainnet Requirement A1 — Voucher slashing. Do not invent a new acronym for a term used only a few times. - Preserve exact technical identifiers. Keep code symbols, commands, environment variables, protocol versions, and external identifiers unchanged inside code formatting. Add a plain-language explanation next to them.
- State limits explicitly. Say what an approval, test, flag, or status permits and what it does not permit.
Label Pattern
Use this pattern when a sequence identifier is necessary:
<scope> <kind> <identifier> — <topic>
Examples:
Base Sepolia Deployment Gate B — Paused deploymentBase Mainnet Requirement A3 — Emergency pause and role custodyWallet Connection Test 4 — Reconnect after session expiryDatabase Migration Mode 2 — Apply guarded schema changes
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.
- 8d ago First seen · 139 lines · 100 tokens per session scan A e4200e99b431
simplified-technical-english is a skill published in the GitHub repository dirtybits/agent-skills (2 stars, last pushed 1mo ago), licensed MIT. It adds 100 tokens to every session and 1,329 once invoked, about $0.0005 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
documentation-patterns
Technical documentation patterns for READMEs, ADRs, API docs (OpenAPI 3.1), changelogs, and writing style guides. Use when creating project documentation, writing architecture decisions, documenting APIs, or maintaining changelogs.
skill-creator
A guide for creating or improving an agent skill: a SKILL.md file that gives an AI a repeatable workflow for a specific task. It covers the skill’s name, search keywords, instructions, failure handling, and examples where needed.
absolute-docs
Diátaxis-driven documentation for AI coding agents: write, improve, or audit tutorials, how-tos, reference, explanation, and developer docs (README, CONTRIBUTING, ADRs). Detects the docs stack; gates on the outline before writing prose; verifies every claim against the code before it ships. Triggers on "absolute…
document-writer
Write or update technical documentation grounded in the real codebase. Use when the user asks for README, API docs, architecture guides, user guides, CONTRIBUTING docs, migration notes, or JSDoc/code comments, or wants technical docs rewritten into natural Chinese with correct terminology. Not for general prose…
Documentation Gap Finder
Audits a codebase or docs folder and lists everything that is undocumented, outdated, or unclear.
technical-writing
Use when drafting or revising internal technical design docs, review notes, architecture writeups, or sharing posts in Chinese, especially when the tone should stay evidence-backed, calm, and suitable for peers or leaders rather than marketing or literary writing.