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-organization-pattern)<a href="https://agentmods.dev/rules/stramp/lost-mines-phandelver/code-organization-pattern"><img src="https://agentmods.dev/badge/rules/stramp/lost-mines-phandelver/code-organization-pattern/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-organization-pattern"><img src="https://agentmods.dev/badge/rules/stramp/lost-mines-phandelver/code-organization-pattern.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.01773 | $0.01773 |
| Opus 5.5 | $0.00709 | $0.00709 |
| Sonnet 5.5 | $0.00355 | $0.00355 |
| Haiku 4.5 | $0.00177 | $0.00177 |
Grade A, and why
code-organization-pattern 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 — 410 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code Organization Pattern
🎯 Objective
ALWAYS organize C++ files following a consistent pattern with:
- Clear section comments
- Regions to group related code
- Includes grouped by category
- Logical organization by responsibility
- Explanatory comments in important functions
📋 Mandatory Structure
1. File Header
ALWAYS start with:
// Copyright Epic Games, Inc. All Rights Reserved.
#pragma once
// ============================================================================
// Includes
// ============================================================================
#pragma region Includes
// Project includes - [categoria]
#include "..."
// Engine includes
#include "..."
#pragma endregion Includes
2. Organization with Regions
ALWAYS use #pragma region to group related code:
// ============================================================================
// [Section Name]
// ============================================================================
#pragma region [Section Name]
// Related code here...
#pragma endregion [Section Name]
3. Section Comments
ALWAYS use section comments with separators:
// ============================================================================
// Section Name
// ============================================================================
Separator pattern:
- Use
===to create visual line - Consistent spacing
- Titles in PascalCase or descriptive
📁 Organization by File Type
.cpp Files (Implementation)
Mandatory structure:
// Copyright Epic Games, Inc. All Rights Reserved.
// ============================================================================
// Includes
// ============================================================================
#pragma region Includes
#include "[Header].h"
// Project includes - [categoria 1]
#include "..."
// Project includes - [categoria 2]
#include "..."
// Engine includes
#include "..."
#if WITH_EDITOR
#include "..."
#endif
#pragma endregion Includes
// ============================================================================
// [Seção Principal 1]
// ============================================================================
#pragma region [Seção Principal 1]
/**
* Comentário explicativo da função.
* Explica o "porquê" e o "como" quando necessário.
*/
void Function1()
{
// Implementação
}
#pragma endregion [Seção Principal 1]
// ============================================================================
// [Seção Principal 2]
// ============================================================================
#pragma region [Seção Principal 2]
// Mais código...
#pragma endregion [Seção Principal 2]
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 · 410 lines · 1,773 tokens per session scan A 230e8a840d94
code-organization-pattern is a cursor rule published in the GitHub repository Stramp/Lost-Mines-Phandelver (2 stars, last pushed 10mo ago), licensed MIT. It adds 1,773 tokens to every session, about $0.0071 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
move-copy-semantics
Avoid std::move(const&) silent copies; use sink-by-value + std::move.
vios-error-security
Error handling and security rules for VIOS C++ code.
cuda
Definitive guidelines for writing high-performance, maintainable, and error-resistant CUDA C++ code, focusing on modern practices, memory management, kernel optimization, and robust error handling.
cpp
Name methods (casing, etc) like "isvalid", "streamtext".
monitor-c-conventions
C coding conventions for HPCPerfStats monitor (C-only).
monitor-c-refactor-standards
Behavior-preserving C refactor standards for HPCPerfStats monitor.