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 agentmods add skills/idjohnson/aiskills/ste100npx skills add idjohnson/aiskills --skill ste100git clone --depth 1 https://github.com/idjohnson/aiskillsWrote 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/idjohnson/aiskills/ste100)<a href="https://agentmods.dev/skills/idjohnson/aiskills/ste100"><img src="https://agentmods.dev/badge/skills/idjohnson/aiskills/ste100.svg" alt="Measured on agentmods" 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.00065 | $0.01868 |
| Opus 5 | $0.00032 | $0.00934 |
| Sonnet 5 | $0.00013 | $0.00374 |
| Haiku 4.5 | $0.00006 | $0.00187 |
Grade A, and why
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 5d 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 — 114 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ASD-STE100 Issue 9 (Simplified Technical English) AI Skill
This skill equips AI assistants with the complete ASD-STE100 Issue 9 (January 2025) specification for preparing technical documentation in controlled English.
Overview & Core Principles
ASD-STE100 Simplified Technical English (STE) is an international standard designed to make technical manuals clear, easy to read, unambiguous, and simple to translate.
Key ASD-STE100 Rules Summary
- Vocabulary (Section 1): Use approved STE dictionary words strictly as their designated Part of Speech and approved meaning. Use Technical Nouns (TN) and Technical Verbs (TV) only from approved categories.
- Noun Clusters (Section 2): Limit multi-word noun clusters to a maximum of 3 words unless it is an official registered technical name.
- Verb Forms (Section 3): Use only simple tenses (Present Simple active, Past Simple active, Future Simple with "will", Imperative, Past Participle as adjective). NO passive voice in procedural writing. NO present continuous (-ing gerunds) except as approved TN/modifiers. NO complex modal auxiliaries (avoid should, could, may, might, shall).
- Sentence Limits (Section 4, 5, 6):
- Procedural text: Maximum 20 words per sentence. One instruction per sentence (unless simultaneous).
- Descriptive text: Maximum 25 words per sentence. Maximum 6 sentences per paragraph. Maximum 1 topic per paragraph.
- No omitted words or contractions: Always include articles (the, a, an) and demonstrative adjectives (this, these). Never use contractions (don't, can't).
- Procedural Writing (Section 5): Start procedural instructions with imperative (command) verbs. Place conditional clauses (If..., When...) at the beginning of the instruction.
- Safety Instructions (Section 7): Use signal words
WARNING(risk of personal injury/death),CAUTION(risk of equipment damage), orNOTE(information only). Always state safety warnings BEFORE the step to which they apply. - Punctuation & Word Count (Section 8): Standard English punctuation is permitted EXCEPT the semicolon (;). Hyphenated words count as one word. Text in parentheses counts as one word in the sentence word count.
- Writing Practices (Section 9): Eliminate phrasal verbs (carry out, put off, take off). Rewrite using approved simple verbs (do, delay, remove).
What ships with it
19 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.
- examples/descriptive_examples.md 1.5 KB
- examples/procedural_examples.md 1.9 KB
- examples/safety_examples.md 1.5 KB
- references/approved_words_list.md 4.9 KB
- references/dictionary.json 625 KB
- references/quick_reference.md 2.7 KB
- references/technical_categories.md 2.2 KB
- references/unapproved_words_map.json 288 KB
- rules/01_words.md 3.9 KB
- rules/02_multi_word_nouns.md 1.3 KB
- rules/03_verbs.md 3.3 KB
- rules/04_sentences.md 1.7 KB
- rules/05_procedural_writing.md 1.8 KB
- rules/06_descriptive_writing.md 965 B
- rules/07_safety_instructions.md 1.2 KB
- rules/08_punctuation_and_word_count.md 2.1 KB
- rules/09_writing_practices.md 1.6 KB
- scripts/dictionary_lookup.py 2.1 KB runs code
- scripts/ste_checker.py 5.6 KB runs code
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.
- 5d ago First seen · 114 lines · 65 tokens per session scan A f57246f718e1
ste100 is a skill published in the GitHub repository idjohnson/aiskills (2 stars, last pushed 1mo ago), licensed MIT. It adds 65 tokens to every session and 1,868 once invoked, about $0.0003 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
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…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
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…
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…