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/Bilal140202/the-lord-of-the-skillsWrote 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/bilal140202/the-lord-of-the-skills/clean-code)<a href="https://agentmods.dev/rules/bilal140202/the-lord-of-the-skills/clean-code"><img src="https://agentmods.dev/badge/rules/bilal140202/the-lord-of-the-skills/clean-code/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/bilal140202/the-lord-of-the-skills/clean-code"><img src="https://agentmods.dev/badge/rules/bilal140202/the-lord-of-the-skills/clean-code.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.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 9d 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.
This is a copy
100% identical to clean-code — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
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.
- 9d ago First seen · 349 lines · 0 tokens per session scan A d74510d4b1ea
clean-code is a cursor rule published in the GitHub repository Bilal140202/the-lord-of-the-skills (4 stars, last pushed 6d ago), licensed MIT. 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. It is 100% identical to clean-code, differing in 0 lines, and is treated as a copy.
Other cursor rules, from other repositories
agentic-clean-code
Language-agnostic agent-oriented clean code: file size limits, grep-friendly names, provenance comments, testability, and error context. Apply when writing or reviewing code in any stack.
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.
cli-error-handling
CLI command error handling patterns.
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.