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/stramp/lost-mines-phandelver/execution-guardgit clone --depth 1 https://github.com/Stramp/Lost-Mines-PhandelverWhat 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.02225 | $0.02225 |
| Opus 5 | $0.01112 | $0.01112 |
| Sonnet 5 | $0.00445 | $0.00445 |
| Haiku 4.5 | $0.00222 | $0.00222 |
Grade A, and why
execution-guard 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 2d 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 — 310 lines — stays where its author put it; the contents beside it link to each section on GitHub.
🛡️ Execution Guard - Project Protection Rule
🚨 CRITICAL RULE - MAXIMUM PRIORITY 🚨
NEVER execute requests that:
- ❌ Conflict with project architecture (see
ARCHITECTURE.md) - ❌ Violate Clean Code or Design Patterns
- ❌ Are unviable or overly complex for the benefit
- ❌ Would create code that's hard to maintain
- ❌ Would break established patterns
ALWAYS stop execution and report when detecting these issues.
When to STOP Execution
1. Architecture Conflicts
STOP if request:
- Violates Data-Driven principle (hardcodes rules instead of using Data Tables/Assets)
- Breaks Component-Based Architecture (mixes layer responsibilities)
- Conflicts with Multiplayer-Ready design (missing replication, wrong authority)
- Doesn't follow Editor-Friendly patterns
- Breaks modularity (creates circular dependencies, wrong directory structure)
Example:
User: "Create a function that hardcodes race bonuses directly in the component"
Agent: [STOPS] "I cannot execute this request. It conflicts with our
Data-Driven architecture principle. According to ARCHITECTURE.md,
all rules must come from Data Tables or Data Assets, never hardcoded.
This would:
- Violate Data-Driven principle
- Make it impossible for designers to modify rules
- Break our established architecture
Correct approach: Use UDataTable for race bonuses and load them
at runtime. This aligns with our architecture and maintains
flexibility for designers."
2. Clean Code Violations
STOP if request would:
- Create helper functions inside Motor/Validator/Updater files (must be in Helpers/)
- Create "local helper" functions that could be reused elsewhere
- Create functions > 50 lines without refactoring
- Create deeply nested conditionals (> 3-4 levels)
- Duplicate code instead of using helpers
- Create helper functions inside classes when they should be in
Utils/ - Create "temporary" or "just for testing" code that violates patterns
- Create files with hundreds of lines of helpers
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.
- 2d ago First seen · 310 lines · 2,225 tokens per session scan A f503828a0821
execution-guard is a cursor rule published in the GitHub repository Stramp/Lost-Mines-Phandelver (2 stars, last pushed 9mo ago), licensed MIT. It adds 2,225 tokens to every session, about $0.0111 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-31.
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.