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/elirancv/cursormd/quality-standardsgit clone --depth 1 https://github.com/elirancv/CursorMDWrote 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/elirancv/cursormd/quality-standards)<a href="https://agentmods.dev/rules/elirancv/cursormd/quality-standards"><img src="https://agentmods.dev/badge/rules/elirancv/cursormd/quality-standards.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.00278 | $0.00278 |
| Opus 5 | $0.00139 | $0.00139 |
| Sonnet 5 | $0.00056 | $0.00056 |
| Haiku 4.5 | $0.00028 | $0.00028 |
Grade A, and why
quality-standards 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
Quality Standards
Every document must meet these standards.
Core Attributes
- Clear – short paragraphs, concrete language, minimal buzzwords
- Structured – sections match how doc will be used
- Relevant – each section earns its place
- Consistent – same terms throughout
- Goal-aware – MVP light, production deep where critical
Tone
Professional but approachable — clear, direct, not salesy.
Language & Audience
Language:
- Default to user's language (Hebrew ↔ Hebrew, English ↔ English)
- If mixed, ask which language to use
Audience Adaptation:
- Engineers → technical, example-rich, implementation details
- Product/stakeholders → outcomes, high-level, business impact
- End users → plain language, step-by-step, task-focused
Ask if unclear: "Primary audience: engineers, product/management, or end users?"
Self-Check Before Finalizing
✅ Specific to THIS project (not generic template) ✅ No filler sections (every part adds value) ✅ [TBD] instead of guesses (no hallucinated details) ✅ Depth matches goal and request (MVP ≠ production depth) ✅ Clear next steps (what reader should do with this)
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 · 37 lines · 278 tokens per session scan A 741b11a2a83c
quality-standards is a cursor rule published in the GitHub repository elirancv/CursorMD (1 stars, last pushed 9mo ago), licensed MIT. It adds 278 tokens to every session, about $0.0014 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
create-rule-agent
This rule is responsible for creating and updating Cursor rules. Cursor rules govern the structure, hierarchy, style and organization of code in a project. This rule should be invoked in Agent mode when: 1. a user wants to create a new cursor rule, 2. a user wants to update or change an existing rule, 3. user wants…
cloudflare-workers-hono-auto
Cloudflare Workers with Hono framework development standards and best practices.
security-scan-agent
This rule provides comprehensive security scanning for dependencies, complementing the dependency analysis rule with deep security insights including CVE analysis, license compliance, and supply chain risk assessment.
cloudflare-workers-auto
Cloudflare Workers development standards and best practices.
changelog-generator-manual
This rule generates a comprehensive changelog.md file by analyzing all git tags and commits, creating a chronological record of all project changes with proper semantic versioning structure. The changelog.md file is stored at the root of the project.
mysql-auto
This rule enforces MySQL-specific best practices to enhance readability, performance, security, and maintainability. It targets MySQL features (e.g., storage engines, character sets) and common pitfalls, and adds concrete guidance for schema design and creation.