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.
npx agentmods add rules/rm2thaddeus/pixel_detective/quick-troubleshooting-indexgit 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/quick-troubleshooting-index)<a href="https://agentmods.dev/rules/rm2thaddeus/pixel_detective/quick-troubleshooting-index"><img src="https://agentmods.dev/badge/rules/rm2thaddeus/pixel_detective/quick-troubleshooting-index.svg" alt="Measured on agentmods" 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 | $0.00009 | $0.01357 |
| Opus 5 | $0.00005 | $0.00678 |
| Sonnet 5 | $0.00002 | $0.00271 |
| Haiku 4.5 | $0.00001 | $0.00136 |
Grade C, and why
quick-troubleshooting-index scanned grade C with 2 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 4d 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
rm -rf .next && npm run dev Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl http://localhost:3025/health How it starts
The opening of the file, as written. The whole thing — 204 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Quick Troubleshooting Index - Sprint 10 Edition
🚨 EMERGENCY: Rapid Issue Resolution
Use this index to quickly find solutions to common problems encountered during Sprint 10.
🔥 HYDRATION ERRORS (Next.js/Chakra UI)
Symptoms:
- Console error: "Text content does not match server-rendered HTML"
- White flash on page load
- Theme switching not working
- Components showing wrong initial state
Quick Fix (30 seconds):
# 1. Clear Next.js cache
rm -rf .next && npm run dev
# 2. Apply mounted state pattern to problem component
const [mounted, setMounted] = useState(false);
useEffect(() => setMounted(true), []);
if (!mounted) return <div>Loading...</div>;
Detailed Solution: frontend/.cursor/rules/nextjs-hydration-prevention.mdc
🔥 BACKEND CIRCULAR IMPORTS
Symptoms:
- "ImportError: cannot import name" during startup
- uvicorn fails to start
- Router files causing import errors
from main import apperrors
Quick Fix (1 minute):
# NEVER do this in routers:
from ..main import app # ❌
# ALWAYS do this instead:
from ..dependencies import get_qdrant_client
def endpoint(client = Depends(get_qdrant_client)): # ✅
Detailed Solution: backend/.cursor/rules/fastapi-dependency-injection.mdc
🔥 MCP BROWSER TOOLS NOT WORKING
Symptoms:
mcp_browser-tools_takeScreenshotfails- "Failed to discover browser connector server"
- "Chrome extension not connected"
- MCP commands timeout
Quick Fix (2 minutes):
# 1. Check Node.js version (must be ≥18)
node --version
# 2. Start server in separate terminal
npx @agentdeskai/browser-tools-server@latest
# 3. Verify server responds
curl http://localhost:3025/health
# 4. Test basic connectivity
mcp_browser-tools_wipeLogs
Detailed Solution: .cursor/rules/mcp-browser-tools-setup.mdc
🔥 API STATE MANAGEMENT ISSUES
Symptoms:
- Race conditions in useEffect
- Inconsistent loading states
- Manual API error handling
- Data not updating consistently
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.
- 4d ago First seen · 204 lines · 9 tokens per session scan C c988da28bdb0
quick-troubleshooting-index is a cursor rule published in the GitHub repository rm2thaddeus/Pixel_Detective (21 stars, last pushed 7mo ago), licensed MIT. It adds 9 tokens to every session and 1,357 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it C with 2 findings (recursive force delete, makes network calls). 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
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.
family-instance-domain-actions
Family instance domain action implementation patterns.