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/renvia-code/best-cursor-rules/clean-codegit clone --depth 1 https://github.com/Renvia-code/best-cursor-rulesWhat 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.01926 |
| Opus 5 | $0.00000 | $0.00963 |
| Sonnet 5 | $0.00000 | $0.00385 |
| Haiku 4.5 | $0.00000 | $0.00193 |
Grade A, and why
clean-code 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 — 349 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Clean Code Best Practices
Overview
| Principle | Description |
|---|---|
| Readability | Code is read more than written |
| Simplicity | Simple is better than complex |
| Consistency | Follow established patterns |
| Testability | Write code that's easy to test |
Naming Conventions
Use Descriptive Names
// ❌ Bad - Unclear names
const d = new Date()
const u = getUser()
function calc(a, b) { return a + b }
// ✅ Good - Clear, descriptive names
const currentDate = new Date()
const authenticatedUser = getUser()
function calculateTotal(price, quantity) { return price * quantity }
Use Consistent Naming Patterns
// Boolean variables: is, has, should, can
const isActive = true
const hasPermission = user.role === 'admin'
const shouldRefresh = lastUpdate < Date.now() - 60000
const canEdit = hasPermission && isActive
// Functions: verb + noun
function getUser(id: string) {}
function createOrder(data: OrderData) {}
function validateEmail(email: string) {}
function calculateDiscount(price: number) {}
// Event handlers: handle + event
function handleClick() {}
function handleSubmit() {}
function handleUserCreated() {}
Functions
Keep Functions Small and Focused
// ❌ Bad - Does too many things
function processOrder(order) {
// Validate order
if (!order.items) throw new Error('No items')
if (!order.userId) throw new Error('No user')
// Calculate total
let total = 0
for (const item of order.items) {
total += item.price * item.quantity
}
// Apply discount
if (order.coupon) {
total *= 0.9
}
// Save to database
db.orders.create({ ...order, total })
// Send email
sendEmail(order.userId, 'Order confirmed')
}
// ✅ Good - Single responsibility
function validateOrder(order: Order): void {
if (!order.items?.length) throw new Error('Order must have items')
if (!order.userId) throw new Error('Order must have userId')
}
function calculateOrderTotal(items: OrderItem[], coupon?: Coupon): number {
const subtotal = items.reduce((sum, item) => sum + item.price * item.quantity, 0)
return coupon ? applyDiscount(subtotal, coupon) : subtotal
}
function processOrder(order: Order): void {
validateOrder(order)
const total = calculateOrderTotal(order.items, order.coupon)
saveOrder({ ...order, total })
notifyUser(order.userId, 'Order confirmed')
}
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 · 349 lines · 0 tokens per session scan A d74510d4b1ea
clean-code is a cursor rule published in the GitHub repository Renvia-code/best-cursor-rules (12 stars, last pushed 9mo ago), licensed CC0-1.0. It costs nothing until one of its globs matches a file; then it loads 1,926 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
ankra-cli
Ankra CLI rules and best practices for managing Kubernetes clusters via the Ankra platform.
cloudflare-email-telegram-cursorrules-prompt-file
Cursor rules for setting up email-to-Telegram forwarding via Cloudflare Email Routing and Workers using the mail2tg CLI.
flutter-riverpod-cursorrules-prompt-file
Cursor rules for Flutter Riverpod.
angular-novo-elements-cursorrules-prompt-file
Cursor rules for Angular development with Novo Elements UI library.
automl-hyperparameter-optimization
AutoML and hyperparameter optimization rules for Python ML projects using Ray Tune, Optuna, PyCaret, and time-series AutoML libraries.
code-guidelines-cursorrules-prompt-file
Cursor rules for code development with guidelines integration.