asd-ste100

asd-ste100 is a skill for Claude Code, Codex from rsturla/eternal-images. It costs 77 tokens per session (640 once invoked), scanned A, original, MIT.

A writing and checking guide for ASD-STE100 Simplified Technical English. This is a controlled form of English that uses short, clear sentences and approved words to reduce misunderstanding.

In plain words
What is it for?
Rewriting or checking documentation, code comments, commit messages, error messages, tool descriptions, and agent instructions. It is not intended for creative or marketing writing.
Why use it?
It helps make technical text easier to understand, including for readers who speak English as a second language. It can also reduce vague or ambiguous wording.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Rewriting or checking documentation, code comments, commit messages, error messages, tool descriptions, and agent instructions. It is not intended for creative or marketing writing.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/rsturla/eternal-images/asd-ste100
Install

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.

Any agent
npx skills add rsturla/eternal-images --skill asd-ste100
Clone the repo
git clone --depth 1 https://github.com/rsturla/eternal-images

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for asd-ste100

README.md
[![agentmods](https://agentmods.dev/badge/skills/rsturla/eternal-images/asd-ste100/github.svg)](https://agentmods.dev/skills/rsturla/eternal-images/asd-ste100)
Your own site
<a href="https://agentmods.dev/skills/rsturla/eternal-images/asd-ste100"><img src="https://agentmods.dev/badge/skills/rsturla/eternal-images/asd-ste100/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.

agentmods 80×15 button for asd-ste100

Your own site · 80×15
<a href="https://agentmods.dev/skills/rsturla/eternal-images/asd-ste100"><img src="https://agentmods.dev/badge/skills/rsturla/eternal-images/asd-ste100.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 77 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 640 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00077 $0.00640
Opus 5 $0.00039 $0.00320
Sonnet 5 $0.00015 $0.00128
Haiku 4.5 $0.00008 $0.00064

Measured 12d ago against content hash dcc90dbb6325, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

asd-ste100 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.

lumina/files/_base/usr/share/workbench/agents/skills/asd-ste100/SKILL.md · 67 lines

How it starts

The opening of the file, as written. The whole thing — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.

ASD-STE100 Simplified Technical English

Simplified Technical English (STE) is a controlled language from the aerospace industry. It uses a set of writing rules and a dictionary of approved words. The goal is text that a reader cannot misread, including a non-native reader.

This skill is an unofficial aid. It does not guarantee full compliance. For disputed words or rules, see the official source at https://asd-ste100.org. A human writer makes the final decision.

When to apply it

Apply STE to technical and procedural text: documentation, code comments, commit messages, tool descriptions, error messages, and agent-to-agent instructions. Do not apply STE to creative writing or marketing copy, where voice and nuance are the point.

Workflow

Do these three steps. Fix the form, but do not change the meaning.

Step 1 — Classify the text

Decide the type of each passage, because the rules differ:

  • Procedure — an instruction to do something. Sentence limit: 20 words.
  • Description — an explanation of a thing or an idea. Sentence limit: 25 words.

Step 2 — Apply the core rules

  • Write short sentences. Keep to the word limit for the text type.
  • Write one instruction per sentence.
  • Use the active voice.
  • Use simple verb tenses: imperative, simple present, simple past, simple future. Do not use -ing verb forms as verbs. Do not use the passive voice in procedures.
  • Use one word for one meaning. Use approved words. See references/word-choice.md.
  • Do not omit articles (a, the) or other words that make the text clear.
  • Put the condition before the instruction. Example: "If the test fails, stop the build."
  • Use the same term for the same thing each time. Do not use synonyms.
  • Use a vertical list for complex or sequential information.

For the full rule set, see references/writing-rules.md.

Step 3 — Verify

Check the result against references/checklist.md. Fix each problem, then check again. Stop when the text meets all rules or when a rule would change the meaning.

Read the full file on GitHub · 67 lines

Files

What ships with it

3 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.

Changes

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.

  1. 12d ago First seen · 67 lines · 77 tokens per session scan A dcc90dbb6325

Subscribe to this mod's changes

asd-ste100 is a skill published in the GitHub repository rsturla/eternal-images (11 stars, last pushed yesterday), licensed MIT. It adds 77 tokens to every session and 640 once invoked, about $0.0004 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.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

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…

microsoft/ai-agents-for-beginners · 200 tokens

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…

vercel/next.js · 95 tokens

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.

microsoft/vscode · 53 tokens

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…

microsoft/vscode · 71 tokens

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…

vercel/next.js · 83 tokens