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/markdown-organization-basic)<a href="https://agentmods.dev/rules/stramp/lost-mines-phandelver/markdown-organization-basic"><img src="https://agentmods.dev/badge/rules/stramp/lost-mines-phandelver/markdown-organization-basic/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/markdown-organization-basic"><img src="https://agentmods.dev/badge/rules/stramp/lost-mines-phandelver/markdown-organization-basic.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.01634 | $0.01634 |
| Opus 5.5 | $0.00654 | $0.00654 |
| Sonnet 5.5 | $0.00327 | $0.00327 |
| Haiku 4.5 | $0.00163 | $0.00163 |
Grade A, and why
markdown-organization-basic 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 — 227 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Markdown Organization Rules - Basic
🎯 Objective
ALWAYS use collapsible system (<details> and <summary>) to organize Markdown files, especially:
- Long reports
- Technical documentation
- Code analysis
- Guides and tutorials
- Files with multiple sections
📋 Mandatory Rules
1. Always Use Collapsibles in Main Sections
ALWAYS organize main sections with <details>:
<details>
<summary style="background-color: #e8e8e8; padding: 4px 8px; border-radius: 4px;"><b>Main Title</b></summary>
> Description or main content here...
>
> More content if necessary...
</details>
Style Pattern for Titles:
- Main titles:
background-color: #e8e8e8; padding: 4px 8px; border-radius: 4px; - Sub-sections:
background-color: #d8d8d8; padding: 3px 6px; border-radius: 3px; - Use
<b>for bold in main titles
2. Hierarchical Structure with Visual Indentation
ALWAYS use nested collapsibles with quote blocks (>) to create visual hierarchy:
<details>
<summary style="background-color: #e8e8e8; padding: 4px 8px; border-radius: 4px;"><b>⚠️ Problemas Encontrados</b></summary>
> Descrição geral dos problemas...
>
> <details>
> <summary style="background-color: #d8d8d8; padding: 3px 6px; border-radius: 3px;">🔴 Crítico (Alta Prioridade)</summary>
>
> > Conteúdo de problemas críticos...
> >
> > - Item 1
> > - Item 2
>
> </details>
>
> <details>
> <summary style="background-color: #d8d8d8; padding: 3px 6px; border-radius: 3px;">🟡 Médio (Média Prioridade)</summary>
>
> > Conteúdo de problemas médios...
> >
> > - Item 1
> > - Item 2
>
> </details>
</details>
Visual Hierarchy:
- Level 1 (Main): Background
#e8e8e8+ Quote block> - Level 2 (Sub-section): Background
#d8d8d8+ Nested quote block>> - Level 3 (Items): Inside
>>to maintain hierarchy
3. Emojis in Summary
ALWAYS use descriptive emojis in <summary> for better visualization:
- 📊 For summaries/statistics
- ✅ For positive points
- ⚠️ For warnings/problems
- 🔴 For critical/high priority
- 🟡 For medium/medium priority
- 🟢 For low/low priority
- 📋 For lists/checklists
- 💡 For tips/suggestions
- 🎯 For objectives/goals
- 📈 For metrics/analysis
- 🔧 For tools/configurations
- 📚 For documentation/references
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 · 227 lines · 1,634 tokens per session scan A 592be9ac55e8
markdown-organization-basic is a cursor rule published in the GitHub repository Stramp/Lost-Mines-Phandelver (2 stars, last pushed 10mo ago), licensed MIT. It adds 1,634 tokens to every session, about $0.0065 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.