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.
git clone --depth 1 https://github.com/Stramp/Lost-Mines-PhandelverWrote 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/stramp/lost-mines-phandelver/clean-code-mandatory)<a href="https://agentmods.dev/rules/stramp/lost-mines-phandelver/clean-code-mandatory"><img src="https://agentmods.dev/badge/rules/stramp/lost-mines-phandelver/clean-code-mandatory/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/rules/stramp/lost-mines-phandelver/clean-code-mandatory"><img src="https://agentmods.dev/badge/rules/stramp/lost-mines-phandelver/clean-code-mandatory.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.02337 | $0.02337 |
| Opus 5.5 | $0.00935 | $0.00935 |
| Sonnet 5.5 | $0.00467 | $0.00467 |
| Haiku 4.5 | $0.00234 | $0.00234 |
Grade A, and why
clean-code-mandatory 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 1mo 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 — 305 lines — stays where its author put it; the contents beside it link to each section on GitHub.
⚠️ CRITICAL RULE - CLEAN CODE AND DESIGN PATTERNS MANDATORY ⚠️
🚨 RULE ZERO - MANDATORY PRE-CODE VALIDATION 🚨
BEFORE writing ANY function, ALWAYS verify:
- Can this function be reused? → Goes to
Utils/orHelpers/ - Is this function pure (no side effects)? → Can be helper
- Is this function in the right place? → Motor only has motor logic, no helpers
- Does this function follow Single Responsibility? → One function = one responsibility
- Is this function testable in isolation? → If not, refactor
🚨 CRITICAL LOCATION RULE:
- MOTOR DOES NOT HAVE HELPERS - Motors (
*Motor.cpp) only contain motor logic - VALIDATOR DOES NOT HAVE HELPERS - Validators only validate
- UPDATER DOES NOT HAVE HELPERS - Updaters only update
- HELPERS DO NOT HAVE MOTOR LOGIC - Helpers are pure and reusable functions
If the function can be a helper → CREATE IN Helpers/, NOT in current file
🚨 ABSOLUTE RULE - NO EXCEPTIONS 🚨
ALWAYS, ALWAYS, ALWAYS apply Clean Code and C++ Design Patterns in ALL situations:
- ✅ Production code
- ✅ Quick tests
- ✅ Prototypes
- ✅ Bug fixes
- ✅ Refactoring
- ✅ New features
- ✅ Any line of code written
NEVER, NEVER, NEVER create code that violates Clean Code or Design Patterns, even if it's:
- ❌ "Just a quick test"
- ❌ "I'll fix it later"
- ❌ "It's temporary"
- ❌ "It works like this"
MANDATORY Principles
1. Helper/Utility Functions
CRITICAL RULE: Any function that can be reused MUST be in a separate helpers/utilities file.
🚨 ABSOLUTE LOCATION RULE:
- ❌ NEVER create helper inside
*Motor.cpp(ex:MulticlassMotor.cpp,PointBuyMotor.cpp) - ❌ NEVER create helper inside
*Validator.cpp(ex:PointBuyValidator.cpp) - ❌ NEVER create helper inside
*Updater.cpp - ✅ ALWAYS create helper in corresponding
*Helpers.h/cpp(ex:MulticlassHelpers.h)
ALWAYS:
- ✅ Helper functions in
Utils/orHelpers/ - ✅ Parameterized functions (without internal state dependency)
- ✅ Pure functions when possible
- ✅ Functions testable in isolation
- ✅ Static functions in helper classes/namespaces
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.
- 1mo ago First seen · 305 lines · 2,337 tokens per session scan A b83aaf27ceca
clean-code-mandatory is a cursor rule published in the GitHub repository Stramp/Lost-Mines-Phandelver (2 stars, last pushed 10mo ago), licensed MIT. It adds 2,337 tokens to every session, about $0.0093 per session on Opus 5.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
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
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.
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.
config-validation-and-normalization
Config validation and normalization responsibilities (defineConfig normalizes, the orm section schema validates and resolves paths, the loader reports per-section diagnostics).
control-plane-descriptors
Control plane descriptor and instance implementation patterns.