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/itshen/xs_vibe_rules/writing-stylegit clone --depth 1 https://github.com/itshen/xs_vibe_rulesWrote 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/itshen/xs_vibe_rules/writing-style)<a href="https://agentmods.dev/rules/itshen/xs_vibe_rules/writing-style"><img src="https://agentmods.dev/badge/rules/itshen/xs_vibe_rules/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 | $0.00000 | $0.00879 |
| Opus 5 | $0.00000 | $0.00439 |
| Sonnet 5 | $0.00000 | $0.00176 |
| Haiku 4.5 | $0.00000 | $0.00088 |
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 5d 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
中文写作风格规范
适用场景：公众号文章、产品文案、对话稿、说明文字、大模型提示词（Prompt）等中文内容创作。
一、标点规范
- 省略号只用半个：
…，禁止用…… - 禁止用「——」：改成逗号、句号，或拆成两句
二、引号规范
- 必须使用中文引号
「」，禁止使用""或"" - 例外：引用发言人说话时可用
"" - 减少引号用量：只在直接引用原话时保留，用于强调或解释的引号一律去掉
三、禁用句式
- ❌ 禁止「不是…而是…」句式，改成正向陈述或拆句
- ❌ 禁止「而不是…」作为句尾收尾
- ❌ 禁止「不是 A，而是 B」的对比强调，直接说 B，必要时把 A 单独成句否定
四、禁用表达
- ❌ 禁止评价他人的话「很简单」「没有夸张」「非常有道理」等，改成平铺转述
- ❌ 禁止网文式情绪词，如「真的刺穿了我」「震撼到了」「我愣住了」「心跳漏了一拍」，改成描述具体感受
- ❌ 禁止解读前置，如「这句话背后其实有一个深层的判断」，直接说判断本身
五、标题规范
- 避免煽情词，改成概念词或动作词
六、写作自查流程（强制要求）
⚠️ 凡是生成了文案内容或大模型提示词（Prompt），交付前必须执行以下自查流程，不可跳过。
触发条件： 以下任意一种情况均需触发：
- 生成了公众号文章、产品文案、对话稿、说明文字等内容
- 编写或修改了用于大模型调用的 System Prompt、User Prompt、Few-shot 示例等
自查步骤（逐项搜索，逐条修改）：
- 搜索以下违禁模式，发现一处改一处，改完再搜下一条：
| 搜索关键词 | 对应规则 | 处理方式 |
|---|---|---|
不是 |
三 | 改成正向陈述，或拆成两句 |
而是 |
三 | 同上，连带检查整句结构 |
而不是 |
三 | 尤其检查是否用作句尾 |
—— |
一 | 改成逗号、句号或拆句 |
…… |
一 | 改成 … |
" 或 " 或 " |
二 | 改成 「」，或确认是否为发言人引用 |
很简单 / 没有夸张 / 非常有道理 |
四 | 删掉评价，改成平铺转述 |
刺穿 / 震撼 / 愣住 / 心跳 |
四 | 改成描述具体感受 |
背后其实 / 深层 / 本质上是 |
四 | 删掉解读前置，直接说结论 |
-
检查标题：是否含煽情词（「震撼」「感动」「泪目」「绝了」等），改成概念词或动作词
-
自查完成后，在交付内容前注明：
✅ 已完成写作规范自查
- ❌ 禁止生成内容后直接交付，跳过自查步骤
- ❌ 提示词同样适用，System Prompt 里的违禁句式也必须修改
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.
- 5d ago First seen · 60 lines · 0 tokens per session scan A eb4c302ae728
writing-style is a cursor rule published in the GitHub repository itshen/xs_vibe_rules (42 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 879 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-30.
Other cursor rules, from other repositories
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.
family-instance-domain-actions
Family instance domain action implementation patterns.
prefer-assertions-over-defensive-checks
Prefer assertions over defensive checks when data is guaranteed to be valid.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.