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.
git clone --depth 1 https://github.com/menonpg/ste-promptWrote 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/commands/menonpg/ste-prompt/ste)<a href="https://agentmods.dev/commands/menonpg/ste-prompt/ste"><img src="https://agentmods.dev/badge/commands/menonpg/ste-prompt/ste/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/commands/menonpg/ste-prompt/ste"><img src="https://agentmods.dev/badge/commands/menonpg/ste-prompt/ste.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.00023 | $0.00308 |
| Opus 5.5 | $0.00009 | $0.00123 |
| Sonnet 5.5 | $0.00005 | $0.00062 |
| Haiku 4.5 | $0.00002 | $0.00031 |
Grade A, and why
ste 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 4d 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.
What it actually says
Rewrite the target text in ASD-STE100 Simplified Technical English (STE).
If the user gave text after the command, rewrite that. Otherwise rewrite your previous answer.
Apply these rules:
- Keep procedural sentences to 20 words or fewer. Keep descriptive sentences to 25 words or fewer.
- Write one instruction per sentence.
- Use the active voice.
- Use the present tense for instructions.
- Start each instruction with the command verb. Example: "Remove the bolt."
- Use articles. Write "the file," not "file."
- Do not use a noun as a verb.
- Use approved words with one meaning each. Prefer:
- obey (not follow, for rules)
- make sure (not ensure)
- remove (not strip out)
- start / stop (not initiate / terminate)
- about (not approximately)
- use (not utilize)
- help (not facilitate)
- before / after (not prior to / subsequent to)
- Write one topic per paragraph. Put the topic sentence first.
- Use a vertical list for more than three steps or conditions.
Keep all facts, numbers, code, and commands exactly the same. Change only the language. Do not add new information. Do not remove any step.
Output only the rewritten text.
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.
- 4d ago First seen · 36 lines · 23 tokens per session scan A 7a4ade807a82
ste is a command published in the GitHub repository menonpg/ste-prompt (41 stars, last pushed 18d ago), licensed MIT. It adds 23 tokens to every session and 308 once invoked, about $0.0001 per session on Opus 5.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-10-22.
Other commands, from other repositories
explain
A guided command for explaining how a file or code section works. It covers its purpose, main logic, data flow, dependencies, design choices, and possible improvements.
explain
Explain complex concepts in simple terms with examples and analogies.
upskill
Find the skill gaps that keep recurring across your applications and turn them into a learning plan.
mock-interview
Rehearse a realistic mock interview, one question at a time.
wiki-teach
Query and learn from the compiled wiki with source-grounded explanations. This is a built-in paper-wiki action.
train
Train a brain locally — an agentic study session, the server only stores notes.