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.
git clone --depth 1 https://github.com/waynesutton/markdown-siteWrote 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/waynesutton/markdown-site/write)<a href="https://agentmods.dev/rules/waynesutton/markdown-site/write"><img src="https://agentmods.dev/badge/rules/waynesutton/markdown-site/write/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/rules/waynesutton/markdown-site/write"><img src="https://agentmods.dev/badge/rules/waynesutton/markdown-site/write.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.00026 | $0.02364 |
| Opus 5.5 | $0.00010 | $0.00946 |
| Sonnet 5.5 | $0.00005 | $0.00473 |
| Haiku 4.5 | $0.00003 | $0.00236 |
Grade A, and why
write 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 — 437 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Writing style rules
Use this rule when writing documentation, README files, comments, commit messages, or any other user facing text.
Triggers
| Trigger | Output |
|---|---|
write:tweet or write:x |
X or Twitter post |
write:linkedin |
LinkedIn post |
write:blog |
Blog post |
write:readme |
README |
write:commit |
Git commit message |
write:docs |
Developer documentation |
write:feature |
Feature post |
write:convex |
Convex specific content |
write:tip |
Quick tip |
Example usage:
- "write:tweet about real time sync"
- "write:blog on authentication patterns"
- "write:feature for our new search API"
Rule of one
Every piece of content follows this framework:
- One person: Write to a specific person, not an audience.
- One problem: State the single problem they face.
- One cause: Identify the root cause.
- One difference: Explain what the solution does differently.
- One action: End with one clear next step.
Rule of one checklist
Before publishing, answer these:
- Can I name the one person this is for?
- Can the problem fit in one sentence?
- Is the root cause obvious?
- Can I explain the difference in one breath?
- Is there only one action at the end?
If any answer is no, revise before publishing.
When to use this rule
Use it for:
- X or Twitter posts
- LinkedIn content
- Blog posts
- README files
- Git commits
- Product announcements
- Developer documentation
- Feature posts
Important: this is for standalone writing. Do not update project files like files.md, changelog.md, or README.md when using this rule.
Voice styles
Pick a voice that fits the output:
| Style | Characteristics | Use for |
|---|---|---|
| Technical educator | Clear, structured, educational | Technical content, tutorials, READMEs |
| Conversational dev | Warm, witty, approachable | Social posts, personal takes |
| Analytical thinker | Data driven, bold, opinionated | Thought leadership, threads |
| Aphorist | Compressed, timeless, pithy | Short posts, one liners |
| Founder voice | Experience backed, energetic | Startup content, advice |
| Systems thinker | Frameworks, mental models | Long form, technical takes |
| Dev culture | Relatable, playful, authentic | Community content, personality |
| Data storyteller | Visual, analytical, trend focused | AI trends, market insights |
| Enterprise pro | Professional, strategic, precise | Enterprise SaaS, B2B content |
| Community builder | Encouraging, personal, supportive | Career growth, DevRel |
| Learn in public | Educational, transparent, iterative | Developer career, web dev |
| Product thinker | Community first, growth minded | Community building, growth |
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 · 437 lines · 26 tokens per session scan A 420716a99155
write is a cursor rule published in the GitHub repository waynesutton/markdown-site (627 stars, last pushed 4mo ago), licensed MIT. It adds 26 tokens to every session and 2,364 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-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.
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.
shared-plane-packages
Pattern for creating shared plane packages that serve both migration and runtime planes.