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 rules/webhook-co/webhook/writing-voicegit clone --depth 1 https://github.com/webhook-co/webhookWhat 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.00000 | $0.00305 |
| Opus 5 | $0.00000 | $0.00152 |
| Sonnet 5 | $0.00000 | $0.00061 |
| Haiku 4.5 | $0.00000 | $0.00030 |
Grade A, and why
writing-voice 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 yesterday.
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
Writing voice
Apply to anything a user reads: docs, dashboard copy, CLI output, error messages, changelogs.
- Precise & quietly opinionated. Have a point of view and state it plainly; recommend the right path instead of listing every option. Sage + Creator, not hype.
- Casual-professional, developer-to-developer. Write like a sharp colleague. Contractions are fine. Cut needless jargon; when a term is necessary, define it once.
- Dry, sparing wit — never at the expense of clarity. If a joke risks confusing the reader, drop the joke.
- Lowercase brand names:
webhook.coandwbhk.my, even at the start of a sentence where it reads naturally. - Sentence case for headings, titles, buttons, and UI labels.
- Tie-breakers: when wording choices conflict, optimize for clarity first, then trust. Be honest about limits and tradeoffs; never overpromise.
- Prefer active voice, short sentences, and concrete examples over abstraction. Lead with what the reader can do.
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.
- yesterday First seen · 24 lines · 305 tokens per session scan A 4563b6404e5a
writing-voice is a cursor rule published in the GitHub repository webhook-co/webhook (0 stars, last pushed 6d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 305 tokens. 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-31.
Other cursor rules, from other repositories
docs
All documentation files use MDX format with a specific structure.
type-inference
Derive TypeScript types from Zod schemas - no hand-written interfaces for wire shapes.
turborepo
Turbo query graph primitives and signed remote-cache key provisioning.
workers-cache
Workers Cache - Cache-Control, gateway exports cache off, RPC vs fetch.
boundaries
Package dependency boundaries - tag map and enforced invariants.
react
React 19 SPA invariants - client-only, no fetch in useEffect, Compiler memo policy.