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 urmzd/dotfiles --skill asd-ste100git clone --depth 1 https://github.com/urmzd/dotfilesWrote 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/urmzd/dotfiles/asd-ste100)<a href="https://agentmods.dev/skills/urmzd/dotfiles/asd-ste100"><img src="https://agentmods.dev/badge/skills/urmzd/dotfiles/asd-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.00118 | $0.01403 |
| Opus 5 | $0.00059 | $0.00701 |
| Sonnet 5 | $0.00024 | $0.00281 |
| Haiku 4.5 | $0.00012 | $0.00140 |
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 7d 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 — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Simplified Technical English (ASD-STE100)
Apply the ASD-STE100 specification (Issue 8) when writing or rewriting technical text. STE is a controlled language: a restricted dictionary plus writing rules that remove ambiguity for readers whose first language is not English and for machine parsing.
When to Use
- The user invokes
/asd-ste100or asks for STE, Simplified Technical English, or controlled language. - The user asks to write or review procedures, work instructions, maintenance steps, or safety warnings that must be unambiguous.
- The user asks to "simplify" documentation explicitly to a controlled standard, not just tidy it.
Core Principles
- One word, one meaning. Each approved word has exactly one meaning and one part of speech. If a word is approved as a noun, do not use it as a verb.
- Approved words only. General vocabulary comes from the STE dictionary (about 900 words). Everything else must qualify as a Technical Name or a Technical Verb.
- Short, direct, active. Short sentences, active voice, one instruction per sentence.
Vocabulary Rules
| Rule | Standard |
|---|---|
| Approved meaning only | Use a dictionary word only in its approved meaning. Example: "fall" means only "to move down by the force of gravity", never "decrease" or "autumn". |
| Approved part of speech | "test" is approved as a noun only: write "Do a test of the system", not "Test the system". |
| Prefer the approved alternative | "start" replaces "begin, commence, initiate". "do" replaces "carry out, perform". "before" replaces "prior to". |
| Technical Names | Nouns specific to the domain (part names, tools, materials, system names) are allowed even if not in the dictionary. Use them consistently and only as nouns. |
| Technical Verbs | Domain-specific actions (e.g. "to calibrate", "to drill") are allowed as verbs when no approved verb exists. |
| No slang or idioms | Remove figurative language, phrasal padding, and Latin abbreviations (write "for example", not "e.g."). |
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.
- 7d ago First seen · 100 lines · 118 tokens per session scan A fb8247d5b21e
asd-ste100 is a skill published in the GitHub repository urmzd/dotfiles (3 stars, last pushed yesterday), licensed Apache-2.0. It adds 118 tokens to every session and 1,403 once invoked, about $0.0006 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
benchling-integration
Benchling Python SDK and REST API integration for registry entities, inventory, ELN entries, workflows, Benchling Apps, and Data Warehouse queries. Use when automating lab data with benchling-sdk or the v2 API.
mcp-notion-usage-guide
A usage guide for connecting AI agents to Notion databases through MCP. Notion is a workspace for documents and databases, while a database view is a saved way of displaying database records.
astropy
Core Python library for astronomy and astrophysics workflows that need Astropy APIs, including units/quantities, coordinates, FITS I/O, tables, time systems, WCS, and cosmology. Use when implementing or debugging astronomical data analysis code with Astropy.
esm
Comprehensive toolkit for EvolutionaryScale protein language models including ESM3 (generative multimodal design across sequence, structure, and function) and ESM C (efficient embeddings). Use for protein sequence/structure/function tasks, inverse folding, embeddings, variant design, and ESMFold2 structure prediction…
ralph-loop
An iterative development workflow that moves from requirements to planning to building, with code review and tests required at each stage.
create-pr
Rebase from the latest origin/main, squash the commits from it, and then create a PR on github with intelligent commit messages based on staged changes.