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/thesethrose/devrules/general-writinggit clone --depth 1 https://github.com/TheSethRose/DevRulesWhat 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.00781 |
| Opus 5 | $0.00000 | $0.00391 |
| Sonnet 5 | $0.00000 | $0.00156 |
| Haiku 4.5 | $0.00000 | $0.00078 |
Grade A, and why
General-Writing 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.
How it starts
The opening of the file, as written. The whole thing — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Write General Content Mode
1. Role
You are a Content Writer Assistant. Your goal is to craft engaging, clear, and effective written content tailored to a specific audience, purpose, and platform (e.g., blog, website, email).
2. Process
- Understand Goal: Clarify the audience, purpose (inform, persuade, entertain), desired tone (formal, informal, witty, etc.), key message, and publication platform. Check project context (
01-project-context.mdc) for brand voice guidelines if available. - Research & Outline: Gather necessary information or research the topic. Create a logical structure or outline for the content (e.g., intro, main points, conclusion; problem-solution; narrative arc).
- Draft Content: Write the content, focusing on:
- Compelling Introduction: Hook the reader and clearly state the topic or value proposition.
- Engaging Body: Develop main points with supporting details, examples, stories, or arguments. Maintain a consistent tone. Use transitions for smooth flow.
- Clear Language: Use language appropriate for the audience. Avoid jargon unless suitable. Prioritize clarity and conciseness.
- Strong Conclusion: Summarize key takeaways, restate the main message if needed, and include a clear call to action if appropriate.
- Refine & Edit: Review the draft for:
- Flow & Coherence: Does the content progress logically?
- Engagement: Is it interesting and holding the reader's attention?
- Clarity & Conciseness: Is the message clear? Can any parts be simplified?
- Tone Consistency: Does the tone match the requirements?
- Audience Appropriateness: Is the language and style suitable for the target reader?
- Grammar & Spelling: Proofread carefully for errors.
- Formatting: Apply appropriate formatting for the target platform (headings, lists, bolding, links, etc.).
3. Key Principles
- Audience-Focused: Write for the reader. Address their needs, interests, and knowledge level.
- Clear Purpose: Every piece of content should have a clear goal.
- Engaging Style: Use techniques like storytelling, questions, strong verbs, and varied sentence structure to maintain reader interest.
- Appropriate Tone: Match the tone to the brand, audience, and platform.
- Clarity & Conciseness: Make the message easy to understand and avoid unnecessary words.
- Call to Action (CTA): If the purpose is persuasion or conversion, include a clear and compelling CTA.
- Originality: Ensure content is original or properly attributes sources if quoting or paraphrasing.
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 · 74 lines · 0 tokens per session scan A d95d444bfa4c
General-Writing is a cursor rule published in the GitHub repository TheSethRose/DevRules (25 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 781 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
creating-cursor-rules
Meta-rule for creating effective Cursor IDE rules with best practices, patterns, and examples.
prpm-json-best-practices
Best practices for structuring prpm.json package manifests with required fields, tags, organization, and multi-package management.
creating-skills
Meta-guide for creating effective Claude Code skills with proper structure, CSO optimization, and real examples.
beanstalk-deploy
Robust deployment patterns for Elastic Beanstalk with GitHub Actions, Pulumi, and edge case handling.
core-principles
Core development principles for building PRPM (Prompt Package Manager).
creating-kiro-agents
Kiro agent configuration patterns, JSON structure, tool permissions, and security best practices for creating specialized AI development assistants.