What is 02-contributor-guide?

A guide for adding new coding rules or changing existing rules in a rules directory. It explains how to choose a category, format an .mdc rule file, test it, and submit it for review.

Use it when maintaining rules for frameworks, languages, backends, testing tools, styling, security, accessibility, or combined technology stacks.

It reduces uncertainty about where a rule belongs and what structure and checks it should follow.

02-contributor-guide — Cursor rule by Renvia-code

Install

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.

agentmods

npx agentmods add rules/renvia-code/best-cursor-rules/02-contributor-guide

Clone the repo

git clone --depth 1 https://github.com/Renvia-code/best-cursor-rules

Made for: Cursor.

Per session 10 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 854 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

Origin original No closer match found in the catalogue.

Token cost

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.00010	$0.00854
Opus 5	$0.00005	$0.00427
Sonnet 5	$0.00002	$0.00171
Haiku 4.5	$0.00001	$0.00085

Measured 2d ago against content hash 70060d3f8667, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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 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.

.cursor/rules/02-contributor-guide.mdc · 162 lines

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 .mdc file
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

Read the full file on GitHub · 162 lines

Changes

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 · 162 lines · 10 tokens per session scan A 70060d3f8667

Subscribe to this mod's changes

02-contributor-guide 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 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. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Code review Security Testing agentic-ai cursor cursorrules opensource vibecode

02-contributor-guide