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/debugginggit clone --depth 1 https://github.com/rm2thaddeus/Pixel_DetectiveWhat 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.00003 | $0.00860 |
| Opus 5 | $0.00002 | $0.00430 |
| Sonnet 5 | $0.00001 | $0.00172 |
| Haiku 4.5 | $0.00000 | $0.00086 |
Grade A, and why
debugging 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.
How it starts
The opening of the file, as written. The whole thing — 78 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Before starting to debug, take your time to explore the files related with the user request.
Once found, use appropriate MCP servers to gather relevant context and debug information:
MCP-Enhanced Debugging Workflow
1. Collect Context & Evidence
- Error Analysis: Capture error messages, logs, stack traces
- File Discovery: Use
grep_searchfor exact matches,codebase_searchfor broader context - Frontend Issues:
- Use Browser Tools MCP to capture console logs (
mcp_browser-tools_getConsoleLogs,mcp_browser-tools_getConsoleErrors) - Capture network errors (
mcp_browser-tools_getNetworkErrors) - Take screenshots (
mcp_browser-tools_takeScreenshot) for visual issues
- Use Browser Tools MCP to capture console logs (
- Database Issues: Use Supabase MCP to query data and check schema integrity
- Library/API Issues: Use Context7 MCP to gather relevant documentation
2. Investigate Root Causes
- List ≥3 hypotheses based on collected evidence
- Confirm via targeted file reading (
cat -n) & project structure (tree) - Frontend Root Causes: Run comprehensive audits (
mcp_browser-tools_runAuditMode) - Performance Issues: Use
mcp_browser-tools_runPerformanceAudit - Database Root Causes: Execute diagnostic SQL queries via Supabase MCP
3. Reuse Patterns & Solutions
- Search for prior fixes or utilities in codebase
- Library Documentation: Use Context7 MCP for up-to-date API examples and troubleshooting guides
- Similar Issues: Use GitHub MCP to search for related issues in project history
4. Analyze Impact & Dependencies
- Trace dependencies and side-effects
- Frontend Impact: Use Browser Control MCP to analyze affected pages/components
- Database Impact: Check foreign key constraints and data integrity via Supabase MCP
- Cross-System Impact: Consider how changes affect multiple MCP domains
5. Propose & Implement Fixes
- Specify file paths, line numbers, code snippets with clear justification
- Clean Debugging Environment: Use
mcp_browser-tools_wipeLogsbefore testing fixes - Database Fixes: Use transactions in Supabase MCP for safe schema/data changes
- Code Changes: Use GitHub MCP for version-controlled implementation
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.
- yesterday First seen · 78 lines · 3 tokens per session scan A ab76e4d73921
debugging is a cursor rule published in the GitHub repository rm2thaddeus/Pixel_Detective (21 stars, last pushed 6mo ago), licensed MIT. It adds 3 tokens to every session and 860 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.
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.
typescript
Changes to these high-fan-out internals can affect every message, delta, element, or rerun. Keep work in them minimal, and benchmark changes with representative stress-test apps.
coolify-ai-docs
Master reference to all Coolify AI documentation in .ai/ directory.
python_lib
Tips and guidelines specific to the development of the Streamlit Python library, not applicable to scripts and e2e tests.
specs
This directory contains product and tech specs for Streamlit features.