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 surendranb/writing-skills --skill asd-ste100git clone --depth 1 https://github.com/surendranb/writing-skillsWrote 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/surendranb/writing-skills/asd-ste100)<a href="https://agentmods.dev/skills/surendranb/writing-skills/asd-ste100"><img src="https://agentmods.dev/badge/skills/surendranb/writing-skills/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/surendranb/writing-skills/asd-ste100"><img src="https://agentmods.dev/badge/skills/surendranb/writing-skills/asd-ste100.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00034 | $0.00599 |
| Opus 5 | $0.00017 | $0.00300 |
| Sonnet 5 | $0.00007 | $0.00120 |
| Haiku 4.5 | $0.00003 | $0.00060 |
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 11d 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 — 56 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ASD-STE100 Simplified Technical English
Control vocabulary and syntax to eliminate ambiguity in technical documentation.
The core rule
One word, one meaning. Imperative voice for instructions. Maximum 20 words per sentence.
Workflow: choose approved STE vocabulary → write imperative command → restrict sentence length to 20 words max → verify zero ambiguity.
Mechanics
- Approved vocabulary. Use only words from the ASD-STE100 dictionary or approved technical nouns.
- Imperative commands. Start steps with an action verb ("Remove the bolt", not "You should remove the bolt").
- Word count limits. Maximum 20 words for procedural sentences; maximum 25 words for descriptive sentences.
- No noun clusters. Maximum of 3 nouns in a sequence (e.g. use "valve control switch" instead of "engine fuel system valve control switch").
- Present tense. Describe current states in present tense; avoid future tense ("The light is on" not "The light will turn on").
- No gerunds in titles. Use simple nouns or infinitives for headings.
- Explicit conditions. Place conditional clauses at the beginning of the sentence ("If the pressure is low, replace the filter").
- Approved modifiers. Avoid vague adjectives like "extreme", "rapid", or "normal" unless quantified.
Verify
- Sentences do not exceed 20 words for procedures
- Every instruction starts with an active imperative verb
- No noun clusters exceeding 3 words
- All technical terms conform to standard dictionary definitions
- Zero ambiguous pronouns (replace "it" or "they" with specific nouns)
Do not
- Use words with multiple meanings (e.g., use "fast" or "secure", avoid "fixed")
- Write conditional clauses after the main action
- Use contractions or colloquialisms
- Use passive voice in maintenance steps
References
For the enforceable limits (sentence/paragraph/noun-cluster caps), safety-text structure (WARNING/CAUTION/NOTE), and punctuation rules, read references/REFERENCE.md when a draft is borderline or needs verification — load on demand, not upfront.
What ships with it
1 file 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.
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.
- 11d ago First seen · 56 lines · 34 tokens per session scan A a9830da781f3
asd-ste100 is a skill published in the GitHub repository surendranb/writing-skills (33 stars, last pushed 9d ago), licensed MIT. It adds 34 tokens to every session and 599 once invoked, about $0.0002 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
domscribe
Work with Domscribe — the pixel-to-code bridge. Use when setting up, initializing, or configuring Domscribe for a project, OR when editing or modifying UI components (React, Vue, Next.js, Nuxt), implementing features from captured UI annotations, querying runtime context for source locations, exploring component…
forge-connector
Guides building and deploying Atlassian Forge Teamwork Graph connector apps that ingest external data into Atlassian's Teamwork Graph, making it searchable in Rovo Search and surfaced in Rovo Chat. Use when the user wants to build a Forge connector, ingest external data into Atlassian, connect a third-party tool (e.g.…
forge-cost-optimizer
Optimizes Atlassian Forge apps to reduce platform consumption and avoid unnecessary costs using Atlassian's "Optimise Forge platform costs" guidance. Use when the user asks to optimize Forge app costs, reduce Forge invocations, lower GB-seconds, reduce storage or log usage, tune memory, replace polling, improve…
forge-app-review
Performs a lightweight pre-release readiness review of Atlassian Forge apps across manifest/module wiring, architecture, runtime compatibility, dependency posture, tests, deploy readiness, and obvious security, cost, or reliability smells. Use when the user asks "review my Forge app", "pre-deploy check", "is this app…
logic-review
Find logic bugs in a single file or function via semi-formal execution tracing (Premises → Trace → Divergence → Trigger → Remedy). Trigger when a user shares code and suspects something is wrong without naming a concrete failure — phrases like "review this", "does this look right", "check this function", "audit this…
logic-health
Sweep a directory, module, or full codebase for logic correctness and produce a scored health dashboard with systemic patterns. Trigger when the user requests a health view — "audit the whole codebase", "health check", "health overview", "logic health overview", "audit src/", "audit auth and payments modules", "where…