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/code-quality)<a href="https://agentmods.dev/rules/stramp/lost-mines-phandelver/code-quality"><img src="https://agentmods.dev/badge/rules/stramp/lost-mines-phandelver/code-quality/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/code-quality"><img src="https://agentmods.dev/badge/rules/stramp/lost-mines-phandelver/code-quality.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.01391 | $0.01391 |
| Opus 5.5 | $0.00556 | $0.00556 |
| Sonnet 5.5 | $0.00278 | $0.00278 |
| Haiku 4.5 | $0.00139 | $0.00139 |
Grade A, and why
code-quality 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 — 182 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code Quality and Organization
General Principles
- ALWAYS write clean and readable code
- ALWAYS follow Unreal Engine standards
- ALWAYS document complex code
- ALWAYS keep functions small and focused
- ALWAYS use descriptive names
Code Organization
File Structure
- One .h and .cpp file per class
- File name = class name
- Organize in subdirectories by functionality:
Characters/- CharactersComponents/- ComponentsUI/- User interfaceGameplay/- Game mechanicsUtils/- Utilities
Organization within Files
-
Header (.h):
- Copyright
- #pragma once
- Includes
- Forward declarations
- UCLASS/USTRUCT/UENUM
- Class with:
- Public: constructor, public functions, public UPROPERTY/UFUNCTION
- Protected: protected functions, protected UPROPERTY/UFUNCTION
- Private: private members
-
Implementation (.cpp):
- Copyright
- Include corresponding header
- Project includes
- Engine includes
- STL includes (if necessary)
- Implementations
Consistent Naming
Classes
- Actors:
Aprefix (ex:AMyCharacter) - UObjects:
Uprefix (ex:UMyComponent) - Structs:
Fprefix (ex:FPlayerStats) - Enums:
Eprefix (ex:EPlayerState) - Interfaces:
Iprefix (ex:IInteractable)
Variables
- Booleans:
bprefix (ex:bIsRunning) - Floats/Ints: PascalCase (ex:
Health,MaxHealth) - Constants:
const+ PascalCase (ex:const float MaxSpeed = 1000.0f)
Functions
- PascalCase (ex:
BeginPlay(),TakeDamage()) - Verbs for actions (ex:
CalculateDamage(),SpawnEnemy()) - Get/Set for properties (ex:
GetHealth(),SetHealth())
Comments and Documentation
When to Comment
- ALWAYS document public functions
- ALWAYS explain "why" not "what"
- ALWAYS document complex or non-obvious code
- NEVER comment obvious code
Comment Format
/**
* Calculates damage based on weapon type and target defense.
*
* @param WeaponType Attacking weapon type
* @param TargetDefense Target defense value
* @return Calculated damage (always >= 0)
*/
float CalculateDamage(EWeaponType WeaponType, float TargetDefense);
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 · 182 lines · 1,391 tokens per session scan A d2218f37442f
code-quality is a cursor rule published in the GitHub repository Stramp/Lost-Mines-Phandelver (2 stars, last pushed 10mo ago), licensed MIT. It adds 1,391 tokens to every session, about $0.0056 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
clean-code-reviewer
Eliminates technical debt using SOLID, DRY, YAGNI, and Addy Osmani production-grade engineering principles. / TR: SOLID, DRY, YAGNI ve Addy Osmani üretim seviyesi mühendislik ilkeleri ile kod kalitesini denetleyen yetenek.
sweep-benchmarks
Audit xrspatial modules for asv benchmark coverage gaps: missing benchmarks, backend parameterization gaps, unrepresentative inputs, broken or silently-skipped benchmarks.
code-review
BMAD BMM Agent: code-review.
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.