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 nuelcyoung/asd-ste100 --skill asd-ste100git clone --depth 1 https://github.com/nuelcyoung/asd-ste100Wrote 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/nuelcyoung/asd-ste100/asd-ste100)<a href="https://agentmods.dev/skills/nuelcyoung/asd-ste100/asd-ste100"><img src="https://agentmods.dev/badge/skills/nuelcyoung/asd-ste100/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.
<a href="https://agentmods.dev/skills/nuelcyoung/asd-ste100/asd-ste100"><img src="https://agentmods.dev/badge/skills/nuelcyoung/asd-ste100/asd-ste100.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.00085 | $0.04286 |
| Opus 5 | $0.00043 | $0.02143 |
| Sonnet 5 | $0.00017 | $0.00857 |
| Haiku 4.5 | $0.00009 | $0.00429 |
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.
How it starts
The opening of the file, as written. The whole thing — 178 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ASD-STE100 Simplified Technical English (STE)
Write, rewrite, and verify technical text against ASD-STE100 Issue 9 (January 2025). STE is a controlled natural language owned by ASD (Aerospace, Security and Defence Industries Association of Europe). It makes technical text unambiguous, easy to understand, and easy to translate. The standard has two parts: 53 writing rules in 9 sections (Part 1) and a controlled dictionary of about 900 approved words (Part 2).
STE is not simplified English for learners. It is a precise standard that requires strong English proficiency to apply. It adds to, but does not replace, a style guide.
When to Apply This Skill
- Rewrite existing technical text (manuals, procedures, warnings) into STE
- Write new STE-compliant procedures or descriptions
- Review text for STE compliance and report violations
- Explain STE rules, the dictionary, or the standard
Rule 0: Meaning Outranks Vocabulary
Before any other step: never change a technical fact, drop a qualifier, delete an object, or invent an agent in order to satisfy the dictionary. STE removes ambiguity; it does not remove content. A sentence built entirely from approved words that states something false or empty is a worse failure than a sentence that keeps one flagged word.
This is the failure mode that makes an STE rewrite look compliant and read plausibly while being wrong. Three signatures to watch for in your own output:
- Nearest-word substitution. "data that can be lost" → "data that can decrease".
decreasewas approved, so it was taken; the definition is now false. Restructure instead: "the quantity of data that the system can lose". - Object amputation. "helps the platform to scale" → "helps the platform to increase". Increase what? A transitive verb keeps its object or the sentence says nothing.
- Hedge deletion. "can be more important" → "is more important". Deleting a modal turns a qualified claim into an absolute one. (And
canis approved — see the verb rules below.)
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.
- 12d ago First seen · 178 lines · 85 tokens per session scan A f1fa42763d0d
asd-ste100 is a skill published in the GitHub repository nuelcyoung/asd-ste100 (23 stars, last pushed 20d ago), licensed MIT. It adds 85 tokens to every session and 4,286 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.
Other skills, from other repositories
keep-the-why
Extract and preserve the reasoning code cannot explain - decisions, rejected alternatives, workarounds, incidents, constraints - plus project setup and maintainer interviews. Not for what changed (see Keep a Changelog) - only why. Also the place for complaints, feedback and settings changes about this skill itself.
review
Adversarial fresh-context review of an increment before it ships. Every finding cites path:line and is re-verified. Use when saying "review", "grill this", or "critique the implementation".
sw-do
Implement a SpecWeave increment task by task through the ledger, with evidence per task and a verified close. Use for "implement this", "start working", "continue the increment", "keep going".
done
Close an increment: ledger check, specweave verify, optional review, then specweave complete. Use when all tasks are done and saying "close increment", "we are done", or "finish up".
summarize
A guide for turning conversations, logs, documents, or investigation notes into short, action-oriented summaries. It requires conclusions to be tied to available evidence and distinguishes confirmed facts from items still needing confirmation.
pre-modification-check
Use before modifying, refactoring, moving, or deleting files in a Repowise-indexed repository, especially shared utilities, core modules, public APIs, or files the user did not explicitly identify.