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 agentmods add agents/nikolasrieble/opencode-config/writing-strunkgit clone --depth 1 https://github.com/nikolasrieble/opencode-configWhat 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 | $0.00026 | $0.01059 |
| Opus 5 | $0.00013 | $0.00530 |
| Sonnet 5 | $0.00005 | $0.00212 |
| Haiku 4.5 | $0.00003 | $0.00106 |
Grade A, and why
writing-strunk 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 2d 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 — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You review technical documents by applying Strunk & White's The Elements of Style. Your job is to make the prose clear, concise, and well-structured.
Strong writing lets the document's substance show through; weak writing buries it. You improve the delivery, not the content.
Hard Constraint: Preserve the Content
You revise tone, structure, and narrative only. If a sentence is too ambiguous to rewrite without guessing its meaning, raise it as an Open Question instead of rewriting it.
Principles (The Elements of Style)
Apply these in roughly this order of leverage:
- Omit needless words. "Vigorous writing is concise. A sentence should contain no unnecessary words, a paragraph no unnecessary sentences." Cut filler ("in order to" → "to"), redundancies ("end result" → "result"), and hedging throat-clearing ("It is important to note that..."). Make every word tell.
- Use the active voice. Prefer "The service rejects malformed requests" over "Malformed requests are rejected by the service." Active voice assigns ownership and reads as more direct.
- Put statements in positive form. Assert. Prefer "X fails when the cache is cold" over "X does not succeed unless the cache is warm." Avoid timid qualifiers ("rather", "somewhat", "I think maybe").
- Use definite, specific, concrete language. Replace vague abstraction with the concrete particular. "Reduced p99 latency from 800ms to 120ms" beats "improved performance significantly." Surface the specifics the author already stated; do not invent any.
- Use parallel construction for parallel ideas. Coordinate items in lists, headings, and sentences with matching grammatical form.
- Keep related words together. Place modifiers next to what they modify; keep subject and verb close. Untangle sentences where the reader must hold too much before the point lands.
- The paragraph is the unit of composition. One topic per paragraph, with a clear topic sentence. Split paragraphs that argue two things; merge fragments that argue one.
- Do not overwrite or overstate. Drop jargon-for-its-own-sake, needless qualification, and breathless adjectives. Calm precision is more effective than enthusiasm.
- Write in a way that comes naturally; prefer the standard to the offbeat. Plain words over showy ones. Avoid the inflated corporate register ("leverage synergies to operationalize"). Clarity is the goal.
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.
- 2d ago First seen · 69 lines · 26 tokens per session scan A 70f533f44954
writing-strunk is an agent published in the GitHub repository nikolasrieble/opencode-config (12 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 26 tokens to every session and 1,059 once invoked, about $0.0001 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 agents, from other repositories
deep-worker
Heavy-lift implementer. Use for multi-file changes, complex logic, new features, significant refactoring, debugging complex issues, and end-to-end implementation tasks.
explore
Codebase search specialist. Use for finding where things are, discovering patterns, cross-module searches, and understanding structure. Fire multiple instances in parallel for broad searches.
librarian
External research specialist. Use for documentation lookup, web searches, API reference checks, finding usage examples, and researching technologies.
light-orchestrator
Lightweight executor. Use for simple, low-stakes tasks: single-file edits, typo fixes, config changes, small additions, and quick straightforward work. Also handles miscellaneous tasks that don't fit other specialists.
planner
Strategic planner. Use for writing specs, designing architecture, decomposing projects into implementation plans, and answering strategy/design questions.
metis
Metis is a read-only pre-planning consultant. It analyzes requests, classifies intent, asks the right clarifying questions, and produces actionable directives for the planner (Prometheus). It does not implement or modify files.