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 hugobowne/show-us-your-agent-skills --skill writing-stylegit clone --depth 1 https://github.com/hugobowne/show-us-your-agent-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/hugobowne/show-us-your-agent-skills/writing-style)<a href="https://agentmods.dev/skills/hugobowne/show-us-your-agent-skills/writing-style"><img src="https://agentmods.dev/badge/skills/hugobowne/show-us-your-agent-skills/writing-style/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/hugobowne/show-us-your-agent-skills/writing-style"><img src="https://agentmods.dev/badge/skills/hugobowne/show-us-your-agent-skills/writing-style.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.00058 | $0.01412 |
| Opus 5 | $0.00029 | $0.00706 |
| Sonnet 5 | $0.00012 | $0.00282 |
| Haiku 4.5 | $0.00006 | $0.00141 |
Grade A, and why
writing-style 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 12d 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 — 115 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Core Rules
Strip every sentence to its cleanest components. Every word must earn its place.
No throat-clearing. Start with the point, not a warm-up. Cut openings like "In this post, I'll show you..." or "It's worth noting that...". Just say the thing.
No nounism. Use verbs, not noun clusters. "We made a decision to implement" → "We decided to implement." "The establishment of a connection" → "Connecting."
No clutter. Eliminate:
- Qualifiers: "very", "really", "quite", "somewhat", "rather"
- Filler phrases: "in order to", "the fact that", "it is important to note"
- Redundancies: "past history", "future plans", "completely eliminate"
Active voice. "The bug was fixed by the team" → "The team fixed the bug."
Concrete over abstract. Show specifics, not generalizations. "Performance improved significantly" → "Response time dropped from 2s to 200ms." Only if you have direct information in the source material.
Short sentences, short paragraphs. One idea per sentence. Dense paragraphs lose readers.
First person, direct. "I built...", "We discovered...", "The code does X."
No corrective constructions. Don't say "It's not X, it's Y". Just say Y.
No em dashes. They signal AI writing. Use periods, commas, or parentheses instead.
No dead constructions. "There are three reasons" → "Three reasons". "It is important to" → cut entirely or rephrase. These delay the subject.
No weasel words. "Some users reported" → "Users reported" or give the number. "Often" and "generally" hedge without adding. Commit or cut.
Strong verbs. Replace weak verbs (is, was, has, make, do, get) with specific ones. "The function does validation" → "The function validates." "We made improvements" → "We improved."
Unity. One tense, one voice, one mood. Don't drift between past and present, or between "I" and "we" and "you". Pick and stick.
Parallel structure. Lists and comparisons must match grammatically. "Fast, reliable, and it scales well" → "Fast, reliable, and scalable."
Rhythm matters, but sparingly. Vary sentence length for flow. Don't let it become sing-song.
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.
- 12d ago First seen · 115 lines · 58 tokens per session scan A de6ff370ba0c
writing-style is a skill published in the GitHub repository hugobowne/show-us-your-agent-skills (67 stars, last pushed 1mo ago), licensed MIT. It adds 58 tokens to every session and 1,412 once invoked, about $0.0003 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…