agentmods.dev

projectrules

projectrules is a cursor rule for Cursor from rm2thaddeus/Pixel_Detective. It costs 2 tokens per session (334 once invoked), scanned A, original, MIT.

Project rules for keeping code comments and documentation accurate, including notes about recurring bugs and important implementation decisions.

In plain words
What is it for?
Use them when changing code, documenting dependencies or optimizations, and recording the cause and fix for bugs that have appeared more than once.
Why use it?
They reduce repeated mistakes by preserving useful explanations in the code and adding troubleshooting notes when the same problem returns.

Cursor rule for Cursor

Written for Cursor: installed under .cursor/.

not rated 21repo 8mo ago A scan 2 tokens original MIT

Good fit Use them when changing code, documenting dependencies or optimizations, and recording the cause and fix for bugs that have appeared more than once.

Compare 6 cursor rules from other repositories ↓
Install with agentmods
npx agentmods add rules/rm2thaddeus/pixel_detective/projectrules
View source ↗ rm2thaddeus/Pixel_Detective rm2thaddeus.github.io
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.

Clone the repo
git clone --depth 1 https://github.com/rm2thaddeus/Pixel_Detective

Made for: Cursor.

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

agentmods badge for projectrules

README.md
[![agentmods](https://agentmods.dev/badge/rules/rm2thaddeus/pixel_detective/projectrules/github.svg)](https://agentmods.dev/rules/rm2thaddeus/pixel_detective/projectrules)
Your own site
<a href="https://agentmods.dev/rules/rm2thaddeus/pixel_detective/projectrules"><img src="https://agentmods.dev/badge/rules/rm2thaddeus/pixel_detective/projectrules/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.

agentmods 80×15 button for projectrules

Your own site · 80×15
<a href="https://agentmods.dev/rules/rm2thaddeus/pixel_detective/projectrules"><img src="https://agentmods.dev/badge/rules/rm2thaddeus/pixel_detective/projectrules.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 2 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 334 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00002 $0.00334
Opus 5.5 $0.00001 $0.00134
Sonnet 5.5 $0.00000 $0.00067
Haiku 4.5 $0.00000 $0.00033

Measured 1mo ago against content hash 83e81884b07f, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

projectrules 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 1mo 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/projectrules.mdc · 46 lines

What it actually says

Cursor AI Project Rules

These project-specific rules ensure that all generated code is well-documented, structured, and prevents repeated mistakes.

Comment Handling Guidelines

  • Preserve all existing comments

    • Never delete or overwrite existing comments.
    • Only append or modify them to add new insights.

  • Enhance documentation over time

    • If a file is modified, update its comments to reflect why and how changes were made.
    • Document new dependencies, optimizations, and potential pitfalls.

  • Explicit troubleshooting notes

    • When a bug is encountered more than once, insert a clear warning comment explaining:
      • The nature of the issue
      • Why it happens
      • How to fix or avoid it

Troubleshooting & Debugging Best Practices

Recurring Bugs Prevention

  • If a bug is fixed multiple times, insert a comment in the affected file to prevent future reoccurrence.
  • Example format:
# WARNING: This function previously caused an off-by-one error due to X.
# Ensure that the index is correctly adjusted when modifying this section.

🤖 AI Assistant Auto-Routing

  • Smart Context Detection: Follow @smart-entry-points for automatic rule selection
  • File-Based Activation: Rules auto-activate based on file patterns
  • Emergency Routing: Errors automatically route to correct solutions
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.

  1. 1mo ago First seen · 46 lines · 2 tokens per session scan A 83e81884b07f

Subscribe to this mod's changes

projectrules is a cursor rule published in the GitHub repository rm2thaddeus/Pixel_Detective (21 stars, last pushed 8mo ago), licensed MIT. It adds 2 tokens to every session and 334 once invoked, about $0.0000 per session on Opus 5.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.

Writing and docs
Related

Other cursor rules, from other repositories

ponytail

Ponytail, lazy senior dev mode. Always pick the simplest solution that works.

DietrichGebert/ponytail · 604 tokens

angular-20

This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.

angular/angular · 0 tokens

dev-standard

Apache Superset development standards and guidelines for Cursor IDE.

apache/superset · 1,147 tokens

prefer-assertions-over-defensive-checks

Prefer assertions over defensive checks when data is guaranteed to be valid.

prisma/orm · 0 tokens

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.

prisma/orm · 0 tokens

shared-plane-packages

Pattern for creating shared plane packages that serve both migration and runtime planes.

prisma/orm · 0 tokens