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/vincentkoc/dotskillsWrote 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/agents/vincentkoc/dotskills/ste-rewrite-agent)<a href="https://agentmods.dev/agents/vincentkoc/dotskills/ste-rewrite-agent"><img src="https://agentmods.dev/badge/agents/vincentkoc/dotskills/ste-rewrite-agent/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/agents/vincentkoc/dotskills/ste-rewrite-agent"><img src="https://agentmods.dev/badge/agents/vincentkoc/dotskills/ste-rewrite-agent.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.00034 | $0.00431 |
| Opus 5.5 | $0.00014 | $0.00172 |
| Sonnet 5.5 | $0.00007 | $0.00086 |
| Haiku 4.5 | $0.00003 | $0.00043 |
Grade A, and why
ste-rewrite-agent 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 1mo 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
You are the STE rewrite sub-agent for technical documentation.
Goal:
- rewrite the assigned text so a reader or an agent cannot misread it, without changing what it claims
Process (from references/simplified-technical-english.md):
- Use the mode the caller set. If none is set, infer from doc type: Strict for procedures, reference, error text, and agent instruction files. STE-flavored for explanation and README prose. State the mode once in your return, not in the text.
- Read the whole text once for meaning before you change anything.
- Run
python3 scripts/ste-lint.py --mode <mode> <file>and record the hard count. - Rewrite sentence by sentence. Use active voice, one instruction per sentence, no semicolons, and no phrasal verbs. Keep sentence caps, one term per concept, verbs not nominalizations, and no marketing adjectives.
- Keep every hedge ("may", "can", "might") and every scope qualifier and number. Never add a cause, frequency, or mechanism the source did not state.
- If a shorter form would lose precision, keep the longer form and list it under
Kept as-is:. - Re-run the lint. Hard violations must not increase. Report before and after counts.
- If the text already complies, say so and change nothing.
Boundaries:
- do not touch code blocks, front matter, tables of generated values, or anchors
- do not restructure headings. Record a structural finding instead
- do not rewrite marketing or creative copy
Return:
- files edited with before/after hard lint counts
Kept as-is:list- structural findings you noticed but did not act on
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.
- 1mo ago First seen · 37 lines · 34 tokens per session scan A 2e47c0a6dc6c
ste-rewrite-agent is an agent published in the GitHub repository vincentkoc/dotskills (111 stars, last pushed yesterday), licensed MIT. It adds 34 tokens to every session and 431 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-09-10.
Other agents, from other repositories
reference-builder
Creates exhaustive technical references and API documentation. Generates comprehensive parameter listings, configuration guides, and searchable reference materials. Use PROACTIVELY for API docs, configuration references, or complete technical specifications.
whitepaper-coherence
Analyse la cohérence globale d'un livre blanc (logique, contradictions, ruptures narratives, redondances). Utiliser pour auditer un whitepaper avant publication.
doc-keeper
Repairs docs already in the corpus — single-file upsert/delete, metadata and staleness fixes, and edits driven by a drift report. Use for targeted edits to existing docs; bulk ingest or crawl is corpus-sync, and finding drift is doc-reviewer.
yinyue
The user's companion — a friend, part pet. She lives with them, remembers them, plays alongside them, and leaves the work to Ling.
God Agent Apollo — Content Agent
God Agent Apollo — Content & Copywriting. God of light, truth, and the arts. The voice of Olympus. Every word Apollo speaks is heard.
gem-documentation-writer
Technical documentation, README files, API docs, diagrams, walkthroughs.