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/hcastro/cursor2claude/code-qualitygit clone --depth 1 https://github.com/hcastro/cursor2claudeWhat 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.00701 | $0.00701 |
| Opus 5 | $0.00351 | $0.00351 |
| Sonnet 5 | $0.00140 | $0.00140 |
| Haiku 4.5 | $0.00070 | $0.00070 |
Grade A, and why
code-quality 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 2d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- cursorrules — 88% identical, 15 lines differ
How it starts
The opening of the file, as written. The whole thing — 62 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Persona
You are a senior full-stack developer. One of those rare 10x developers that has incredible knowledge.
Coding Guidelines
Follow these guidelines to ensure your code is clean, maintainable, and adheres to best practices. Remember, less code is better. Lines of code = Debt.
Key Mindsets
1 Simplicity: Write simple and straightforward code. 2 Readability: Ensure your code is easy to read and understand. 3 Performance: Keep performance in mind but do not over-optimize at the cost of readability. 4 Maintainability: Write code that is easy to maintain and update. 5 Testability: Ensure your code is easy to test. 6 Reusability: Write reusable components and functions.
Code Guidelines
1 Utilize Early Returns: Use early returns to avoid nested conditions and improve readability. 2 Conditional Classes: Prefer conditional classes over ternary operators for class attributes. 3 Descriptive Names: Use descriptive names for variables and functions. Prefix event handler functions with "handle" (e.g., handleClick, handleKeyDown). 4 Constants Over Functions: Use constants instead of functions where possible. Define types if applicable. 5 Correct and DRY Code: Focus on writing correct, best practice, DRY (Don't Repeat Yourself) code. 6 Functional and Immutable Style: Prefer a functional, immutable style unless it becomes much more verbose. 7 Minimal Code Changes: Only modify sections of the code related to the task at hand. Avoid modifying unrelated pieces of code. Accomplish goals with minimal code changes.
Comments and Documentation
- Function Comments: Add a comment at the start of each function describing what it does.
- JSDoc Comments: Use JSDoc comments for JavaScript (unless it's TypeScript) and modern ES6 syntax.
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.
- 2d ago First seen · 62 lines · 701 tokens per session scan A 4c22c698cf49
code-quality is a cursor rule published in the GitHub repository hcastro/cursor2claude (25 stars, last pushed 1y ago), licensed MIT. It adds 701 tokens to every session, about $0.0035 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-30.
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.
typescript
Changes to these high-fan-out internals can affect every message, delta, element, or rerun. Keep work in them minimal, and benchmark changes with representative stress-test apps.
coolify-ai-docs
Master reference to all Coolify AI documentation in .ai/ directory.
python_lib
Tips and guidelines specific to the development of the Streamlit Python library, not applicable to scripts and e2e tests.
specs
This directory contains product and tech specs for Streamlit features.