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/02-contributor-guide)<a href="https://agentmods.dev/rules/bilal140202/the-lord-of-the-skills/02-contributor-guide"><img src="https://agentmods.dev/badge/rules/bilal140202/the-lord-of-the-skills/02-contributor-guide/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/02-contributor-guide"><img src="https://agentmods.dev/badge/rules/bilal140202/the-lord-of-the-skills/02-contributor-guide.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.00010 | $0.00854 |
| Opus 5 | $0.00005 | $0.00427 |
| Sonnet 5 | $0.00002 | $0.00171 |
| Haiku 4.5 | $0.00001 | $0.00085 |
Grade A, and why
02-contributor-guide 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 02-contributor-guide — 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 — 162 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Contributor Guide
Quick Start
- Find the right category in
rules/ - Create or edit an
.mdcfile - Follow the format in
01-rule-format.mdc - Test the rule in a real project
- Submit PR
Adding a New Rule
Step 1: Check if it exists
# Search existing rules
ls rules/**/*.mdc | grep -i "your-topic"
Step 2: Choose the right category
| Category | What belongs here |
|---|---|
frameworks/ |
React, Next.js, Vue, Svelte, Angular, Astro |
languages/ |
TypeScript, Python, Go, Rust, etc. |
backends/ |
Supabase, FastAPI, Express, Django |
mobile/ |
React Native, Flutter, SwiftUI |
styling/ |
Tailwind, CSS modules, shadcn/ui |
testing/ |
Vitest, Jest, Playwright, Cypress |
best-practices/ |
Clean code, security, accessibility |
stacks/ |
Combined presets (T3, LAMP, etc.) |
Step 3: Create the file
# Example: Adding a new framework rule
touch rules/frameworks/remix.mdc
Step 4: Write the rule
Follow the template:
---
description: [What this rule helps with - 1-2 sentences]
globs: ["**/*.tsx", "**/*.ts"]
alwaysApply: false
---
# [Framework/Topic Name]
## Overview
[Brief intro - what, why, when]
## Key Patterns
[The most important stuff first]
## Examples
[Real code examples]
## Common Mistakes
[What to avoid]
Editing Existing Rules
When to edit
✅ Outdated information (old API, deprecated patterns) ✅ Missing important patterns ✅ Incorrect examples ✅ Typos or unclear language
When NOT to edit
❌ Personal preference changes ❌ Adding niche edge cases ❌ Restructuring without clear benefit
Quality Standards
Must Have
- Valid MDC frontmatter
- Clear, tested code examples
- Current for 2025 (latest stable versions)
- Under 500 lines
- No duplicate content from other rules
Nice to Have
- Tables for quick reference
- ✅/❌ do/don't examples
- Links to official docs
- Common gotchas section
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 · 162 lines · 10 tokens per session scan A 70060d3f8667
02-contributor-guide is a cursor rule published in the GitHub repository Bilal140202/the-lord-of-the-skills (4 stars, last pushed 6d ago), licensed MIT. It adds 10 tokens to every session and 854 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to 02-contributor-guide, differing in 0 lines, and is treated as a copy.
Other cursor rules, from other repositories
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.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.