cross-reference-guide

A navigation guide for finding project rules, grouped by areas such as general development, frontend work, debugging, testing, and MCP server use. MCP servers are tools that an coding agent can call for specific tasks.

In plain words
What is it for?
Use it to locate instructions before planning, debugging, testing, building frontend features, or connecting external tools.
Why use it?
It reduces the time spent searching through many rule files and helps identify which guidance applies to a task.

Cursor rule for Cursor

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/rm2thaddeus/pixel_detective/cross-reference-guide
Clone the repo
git clone --depth 1 https://github.com/rm2thaddeus/Pixel_Detective

Made for: Cursor.

Per session 8 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 2,350 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.

ModelPer sessionOnce invoked
Fable 5 $0.00008 $0.02350
Opus 5 $0.00004 $0.01175
Sonnet 5 $0.00002 $0.00470
Haiku 4.5 $0.00001 $0.00235

Measured yesterday against content hash 12d92f9f76be, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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

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/cross-reference-guide.mdc · 217 lines

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

Read the full file on GitHub · 217 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.

  1. yesterday First seen · 217 lines · 8 tokens per session scan A 12d92f9f76be

Subscribe to this mod's changes

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