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 iurysza/android-use --skill strunk-writing-qualitygit clone --depth 1 https://github.com/iurysza/android-useWrote 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/iurysza/android-use/strunk-writing-quality)<a href="https://agentmods.dev/skills/iurysza/android-use/strunk-writing-quality"><img src="https://agentmods.dev/badge/skills/iurysza/android-use/strunk-writing-quality/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/iurysza/android-use/strunk-writing-quality"><img src="https://agentmods.dev/badge/skills/iurysza/android-use/strunk-writing-quality.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.00027 | $0.03450 |
| Opus 5.5 | $0.00011 | $0.01380 |
| Sonnet 5.5 | $0.00005 | $0.00690 |
| Haiku 4.5 | $0.00003 | $0.00345 |
Grade A, and why
strunk-writing-quality 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.
How it starts
The opening of the file, as written. The whole thing — 355 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Strunk Writing Quality
Apply William Strunk Jr.'s principles from The Elements of Style to improve any piece of prose. This skill enforces clarity, concision, and vigor through specific, actionable rules.
For reports, research write-ups, guidance, documentation and summaries, use references/report-writing-style.md.
Philosophy
Good writing is clear, concise, and vigorous. Every rule exists to serve the reader. Strunk's core tenets:
- Clarity above all — The reader must understand exactly what the writer means
- Every word must tell — Vigorous writing is concise; omit needless words
- Reader service — Every construction should aid comprehension and engagement
- Mastery before deviation — Learn the rules thoroughly before breaking them; any violation must be purchased with "compensating merit"
- Form serves meaning — Punctuation, formatting, and spelling carry semantic weight
- Consistency with authority — Follow established conventions unless context demands otherwise
The mature writer knows the rules well enough to break them with purpose and payoff.
Core Principles
1. Be Concise
Vigorous writing is concise. A sentence should contain no unnecessary words, a paragraph no unnecessary sentences.
| Bloated | Concise |
|---|---|
| the question as to whether | whether |
| there is no doubt but that | no doubt / doubtless |
| used for fuel purposes | used for fuel |
| he is a man who | he |
| in a hasty manner | hastily |
| owing to the fact that | since / because |
| in spite of the fact that | though / although |
Avoid: "the fact that" in all its forms. Replace with direct nouns or verbs:
- "the fact that he had not succeeded" → "his failure"
- "the fact that I had arrived" → "my arrival"
Cut redundant words: If a word adds no meaning, remove it.
What ships with it
2 files 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.
- 1mo ago First seen · 355 lines · 27 tokens per session scan A 0524210ee1ca
strunk-writing-quality is a skill published in the GitHub repository iurysza/android-use (21 stars, last pushed 16d ago), licensed MIT. It adds 27 tokens to every session and 3,450 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-15.
Other skills, from other repositories
babysit
Use when a user asks to babysit, monitor, keep checking, keep an eye on, or report when a pull request, CI run, ticket, deployment, or other changing target reaches an outcome.
rubber-duck
Adversarial "rubber duck" review that turns explaining-out-loud into a hallucination check. The main session is the PRESENTER (it did the work — a design doc, investigation, or analysis — and holds the real reasoning) and reconstructs the topic to a LISTENER — a spawned subagent pinned to a DIFFERENT-vendor model that…
building-agents
Use when building or restructuring an LLM agent — provider adapter, tool calling, structured output, RAG, agent loop, eval gate, cost routing, tracing, MCP server — model-agnostic across OpenAI/Anthropic/Gemini/OSS so a model swap is a config change. NOT vector-store SQL alone (that is postgresdb) or service…
agent-eval
Use when measuring whether an LLM or agent system actually got better and gating merges on it: golden sets, fixing an inflated LLM-as-judge, scoring RAG (faithfulness, contextual recall) or agent trajectories (tool correctness, completion), or picking an eval framework. NOT building the agent loop, tools or RAG…
browser-qa
Testing web apps through a real browser: reconnaissance before acting, selector discovery, state capture, console errors and screenshot evidence. Use on a web surface end to end, or to reproduce a front-end bug.
code-review
Reviewing code for defects: diff-first reading, severity classification, evidence over inference, finding caps, and terminal verdicts. Use when reviewing a diff, PR, or patch, or auditing someone else's work.