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/auto-activation-configgit 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/auto-activation-config)<a href="https://agentmods.dev/rules/rm2thaddeus/pixel_detective/auto-activation-config"><img src="https://agentmods.dev/badge/rules/rm2thaddeus/pixel_detective/auto-activation-config.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.00005 | $0.01185 |
| Opus 5 | $0.00003 | $0.00593 |
| Sonnet 5 | $0.00001 | $0.00237 |
| Haiku 4.5 | $0.00001 | $0.00119 |
Grade A, and why
auto-activation-config 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 3d 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 — 181 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Auto-Activation Configuration - Universal Rule Application
🎯 Mandatory Rule Auto-Activation
This configuration ensures critical rules are automatically applied without manual intervention.
Universal Auto-Activation Rules
PowerShell Syntax Auto-Activation (Windows Users)
rule_name: "powershell-syntax"
activation_trigger: "ALWAYS"
conditions:
- user_os: "win32"
- shell_detected: "PowerShell"
- tool_usage: "run_terminal_cmd"
activation_mode: "preventive"
description: "Automatically prevents PowerShell syntax errors"
mandatory: true
bypass_allowed: false
auto_behaviors:
- split_compound_commands: true
- quote_all_paths: true
- add_workspace_navigation: true
- validate_powershell_compatibility: true
Sprint Lessons Auto-Activation (All Users)
rule_name: "sprint-lessons-learned"
activation_trigger: "development_work"
conditions:
- work_type: ["frontend", "backend", "fullstack"]
- file_modifications: true
activation_mode: "contextual"
description: "Always check Sprint 10 lessons before development"
mandatory: true
bypass_allowed: false
MCP Setup Auto-Activation (Frontend Work)
rule_name: "mcp-browser-tools-setup"
activation_trigger: "frontend_context"
conditions:
- file_patterns: ["frontend/**/*", "**/*.tsx", "**/*.jsx"]
- work_type: ["frontend", "debugging", "testing"]
activation_mode: "contextual"
description: "Verify MCP setup before frontend work"
mandatory: true
bypass_allowed: false
AI Assistant Integration Instructions
Automatic Rule Loading Protocol
# AI assistants MUST follow this sequence:
1. **Detect User Environment**
- Check user OS (win32 → PowerShell rule mandatory)
- Check file context (frontend → MCP setup required)
- Check work type (development → Sprint lessons required)
2. **Auto-Load Mandatory Rules**
- Load rules based on environment detection
- Apply rules BEFORE generating any commands
- Cannot proceed without mandatory rule compliance
3. **Seamless Integration**
- Mandatory rules work WITH context-specific rules
- No rule conflicts or overrides
- Transparent to user (they don't see rule activation)
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.
- 3d ago First seen · 181 lines · 5 tokens per session scan A fe483c11a911
auto-activation-config is a cursor rule published in the GitHub repository rm2thaddeus/Pixel_Detective (21 stars, last pushed 7mo ago), licensed MIT. It adds 5 tokens to every session and 1,185 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.
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.