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/giang6283623/minimal-vibe-coding-kit/050-writing-stylegit clone --depth 1 https://github.com/giang6283623/minimal-vibe-coding-kitWrote 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/rules/giang6283623/minimal-vibe-coding-kit/050-writing-style)<a href="https://agentmods.dev/rules/giang6283623/minimal-vibe-coding-kit/050-writing-style"><img src="https://agentmods.dev/badge/rules/giang6283623/minimal-vibe-coding-kit/050-writing-style.svg" alt="Measured on agentmods" 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.00342 | $0.00342 |
| Opus 5 | $0.00171 | $0.00171 |
| Sonnet 5 | $0.00068 | $0.00068 |
| Haiku 4.5 | $0.00034 | $0.00034 |
Grade A, and why
050-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 6d 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
Writing style rules
- Never use emoji in responses, code, comments, commit messages, docs, or diagrams unless the user explicitly asks for them.
- Do not use em dashes or en dashes in generated prose. Use ASCII punctuation instead: comma, colon, semicolon, hyphen, or parentheses.
- Apply the rule to everything you write: chat responses, documentation, skill files, Mermaid diagram labels, and code comments.
- Exceptions: verbatim quotes of existing content, strings pinned by validators or tests, and files whose established style already uses these characters. When editing such files, keep existing characters and apply the rule only to new text.
- If the user requests a cleanup of existing emoji or dashes, propose the diff first and confirm the validation command in
backbone.ymlstill passes. - Plain-language register in every reply language: lead with the outcome, keep sentences short with one idea each, prefer active voice and concrete verbs, put known information before new information, and define project terms at first use.
- Reuse the project's vocabulary from the glossary named in
backbone.ymlproject.contextwhen present instead of rotating synonyms. When replying in English, keep one meaning per word (ASD-STE100-style simplicity); never apply English-only word lists to other languages. - Reply in the user's conversation language; quote code identifiers, commands, file paths, and error text verbatim in every language. When a message does not land, the user can invoke
/wait-whatfor a plain-language re-pitch.
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.
- 6d ago First seen · 16 lines · 342 tokens per session scan A c8dac1148dce
050-writing-style is a cursor rule published in the GitHub repository giang6283623/minimal-vibe-coding-kit (21 stars, last pushed 8d ago), licensed MIT. It adds 342 tokens to every session, about $0.0017 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 cursor rules, from other repositories
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
cli-error-handling
CLI command error handling patterns.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.
family-instance-domain-actions
Family instance domain action implementation patterns.