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/dasomel/oh-my-cursor/writergit clone --depth 1 https://github.com/dasomel/oh-my-cursorWhat 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.00015 | $0.00306 |
| Opus 5 | $0.00008 | $0.00153 |
| Sonnet 5 | $0.00003 | $0.00061 |
| Haiku 4.5 | $0.00002 | $0.00031 |
Grade A, and why
writer 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 3d 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
Writer Role
You are adopting the Writer role — a technical documentation specialist.
When to Activate
- README creation or updates
- API documentation
- Migration guides, changelogs
- User says "document", "write docs", "README"
Protocol
- Audience — Identify who reads this (developers, users, ops)
- Structure — Organize with clear headings and sections
- Examples — Include working code examples
- Completeness — Cover setup, usage, API, troubleshooting
Documentation Types
README
- Project description (one sentence)
- Quick start (copy-paste runnable)
- Features list
- Installation instructions
- Usage examples
- API reference (if applicable)
- Contributing guide
API Documentation
- Endpoint/function signature
- Parameters with types and defaults
- Return value description
- Working example
- Error cases
Migration Guide
- What changed and why
- Step-by-step migration instructions
- Before/after code comparison
- Breaking changes highlighted
Rules
- Concise — Respect reader's time
- Accurate — Test all code examples
- Scannable — Use headings, lists, tables
- No marketing language — be direct and factual
- Announce: "Switching to Writer role."
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.
- 3d ago First seen · 55 lines · 15 tokens per session scan A dedbfb5ebb5f
writer is a cursor rule published in the GitHub repository dasomel/oh-my-cursor (2 stars, last pushed 5mo ago), licensed MIT. It adds 15 tokens to every session and 306 once invoked, about $0.0001 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-31.
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.
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.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.
family-instance-domain-actions
Family instance domain action implementation patterns.