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/rajitsaha/100xprismWrote 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/rajitsaha/100xprism/copy-editing)<a href="https://agentmods.dev/rules/rajitsaha/100xprism/copy-editing"><img src="https://agentmods.dev/badge/rules/rajitsaha/100xprism/copy-editing/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/rajitsaha/100xprism/copy-editing"><img src="https://agentmods.dev/badge/rules/rajitsaha/100xprism/copy-editing.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.02584 | $0.02584 |
| Opus 5.5 | $0.01034 | $0.01034 |
| Sonnet 5.5 | $0.00517 | $0.00517 |
| Haiku 4.5 | $0.00258 | $0.00258 |
Grade A, and why
copy-editing 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 — 294 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Copy Editing
Systematically improve existing marketing copy through focused editing passes while preserving the core message.
Core Philosophy
Product context: If .agents/product-marketing-context.md exists (or .claude/product-marketing-context.md in older setups), read it first and tailor output to it; only ask for what it doesn't cover.
Editing is enhancing, not rewriting. Key principles: don't change the core message; multiple focused passes beat one unfocused review; every edit needs a clear reason; preserve the author's voice while improving clarity.
The Seven Sweeps Framework
Edit through seven sequential passes, one dimension each. After each sweep, loop back to check previous sweeps aren't compromised.
Sweep 1: Clarity
Focus: Can the reader understand what you're saying?
Check: confusing sentence structures, unclear pronoun references, jargon or insider language, ambiguous statements, missing context.
Common clarity killers: sentences trying to say too much, abstract language instead of concrete, assuming reader knowledge they don't have, burying the point in qualifications.
Process: Read through quickly, highlighting unclear parts without correcting yet. Then recommend specific edits and verify they maintain the original intent.
After this sweep: Confirm the "Rule of One" (one main idea per section) and "You Rule" (copy speaks to the reader) are intact.
Sweep 2: Voice and Tone
Focus: Is the copy consistent in how it sounds?
Check: shifts between formal and casual, inconsistent brand personality, jarring mood changes, word choices that don't match the brand.
Common voice issues: starting casual then becoming corporate, mixing "we" and "the company," unintentional humor/serious swings, technical language appearing randomly.
Process: Read aloud to hear inconsistencies, mark unexpected tone shifts, smooth transitions, keep personality throughout.
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 · 294 lines · 2,584 tokens per session scan A 0dcd0a951829
copy-editing is a cursor rule published in the GitHub repository rajitsaha/100xprism (10 stars, last pushed 5d ago), licensed MIT. It adds 2,584 tokens to every session, about $0.0103 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-09-03.
Other cursor rules, from other repositories
checkpoint
Persistent memory archival — save discoveries to prevent amnesia across sessions.
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.