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/rm2thaddeus/Pixel_DetectiveWrote 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/rm2thaddeus/pixel_detective/cross-reference-guide)<a href="https://agentmods.dev/rules/rm2thaddeus/pixel_detective/cross-reference-guide"><img src="https://agentmods.dev/badge/rules/rm2thaddeus/pixel_detective/cross-reference-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/rm2thaddeus/pixel_detective/cross-reference-guide"><img src="https://agentmods.dev/badge/rules/rm2thaddeus/pixel_detective/cross-reference-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.00008 | $0.02350 |
| Opus 5.5 | $0.00003 | $0.00940 |
| Sonnet 5.5 | $0.00002 | $0.00470 |
| Haiku 4.5 | $0.00001 | $0.00235 |
Grade A, and why
cross-reference-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 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.
How it starts
The opening of the file, as written. The whole thing — 217 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cross-Reference Guide - Comprehensive Rule Navigation
🗺️ RULE ECOSYSTEM OVERVIEW
Your .cursor rules are organized into 3 tiers with cross-cutting concerns:
🏢 PROJECT-WIDE (.cursor/rules/)
├── 🔥 sprint-lessons-learned.mdc # Master reference - Sprint 10 failures
├── ⚡ quick-troubleshooting-index.mdc # Emergency rapid resolution
├── 🧪 sprint10-testing-patterns.mdc # Prevention through testing
├── 🔧 mcp-browser-tools-setup.mdc # 3-component MCP protocol
├── 📋 sprint-planning.mdc # Sprint workflow & planning
├── 🌐 use-mcp-servers.mdc # MCP server integration
├── 🐛 debugging.mdc # General debugging protocols
├── 💬 commentsoverwrite.mdc # Documentation standards
└── 📖 cross-reference-guide.mdc # This navigation guide
🎨 FRONTEND (frontend/.cursor/rules/)
├── 📋 frontend-development-index.mdc # Master index - START HERE for frontend work
├── 💧 nextjs-hydration-prevention.mdc # Server/client consistency
├── 🔄 react-query-api-integration.mdc # Server state management
├── 🏗️ component-architecture-patterns.mdc # Component design & composition patterns
├── 🎨 ux-workflow-patterns.mdc # User experience & workflow patterns
└── ⚡ nextjs-performance-optimization.mdc # Next.js performance optimization
⚙️ BACKEND (backend/.cursor/rules/)
├── 📋 backend-development-index.mdc # Master index - START HERE for backend work
├── 🔗 fastapi-dependency-injection.mdc # Circular import prevention
├── 🏗️ fastapi-microservice-patterns.mdc # Complete service architecture patterns
├── 🤖 ml-service-integration.mdc # GPU-optimized ML service patterns
└── 🔌 api-design-patterns.mdc # RESTful API design & data modeling
🎯 SCENARIO-BASED NAVIGATION
🚨 "I Have an Emergency Issue"
START HERE: .cursor/rules/quick-troubleshooting-index.mdc
- 30-second fixes for common Sprint 10 problems
- Diagnostic flowchart to route you to detailed solutions
- Severity levels to prioritize fixes
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.
- 1mo ago First seen · 217 lines · 8 tokens per session scan A 12d92f9f76be
cross-reference-guide is a cursor rule published in the GitHub repository rm2thaddeus/Pixel_Detective (21 stars, last pushed 8mo ago), licensed MIT. It adds 8 tokens to every session and 2,350 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.
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.
prefer-assertions-over-defensive-checks
Prefer assertions over defensive checks when data is guaranteed to be valid.
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.
shared-plane-packages
Pattern for creating shared plane packages that serve both migration and runtime planes.