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/markdown-organizationgit 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)<a href="https://agentmods.dev/rules/stramp/lost-mines-phandelver/markdown-organization"><img src="https://agentmods.dev/badge/rules/stramp/lost-mines-phandelver/markdown-organization.svg" alt="Measured on agentmods" 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 | $0.03406 | $0.03406 |
| Opus 5 | $0.01703 | $0.01703 |
| Sonnet 5 | $0.00681 | $0.00681 |
| Haiku 4.5 | $0.00341 | $0.00341 |
Grade A, and why
markdown-organization 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 3d 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 — 471 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Markdown Organization Rules
🎯 Objetivo
ALWAYS usar sistema de colapse (<details> e <summary>) para organizar arquivos Markdown, especialmente:
- Relatórios longos
- Documentação técnica
- Análises de código
- Guias e tutoriais
- Arquivos com múltiplas seções
📋 Regras Obrigatórias
1. Sempre Usar Colapsos em Seções Principais
ALWAYS organizar seções principais com <details>:
<details>
<summary style="background-color: #e8e8e8; padding: 4px 8px; border-radius: 4px;"><b>Título Principal</b></summary>
> Descrição ou conteúdo principal aqui...
>
> Mais conteúdo se necessário...
</details>
Padrão de Estilo para Títulos:
- Títulos principais:
background-color: #e8e8e8; padding: 4px 8px; border-radius: 4px; - Sub-seções:
background-color: #d8d8d8; padding: 3px 6px; border-radius: 3px; - Usar
<b>para negrito nos títulos principais
2. Estrutura Hierárquica com Tabulação Visual
ALWAYS usar colapsos aninhados com blocos de citação (>) para criar hierarquia visual:
<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>
Hierarquia Visual:
- Nível 1 (Principal): Fundo
#e8e8e8+ Bloco de citação> - Nível 2 (Sub-seção): Fundo
#d8d8d8+ Bloco de citação aninhado>> - Nível 3 (Itens): Dentro de
>>para manter hierarquia
3. Emojis no Summary
ALWAYS usar emojis descritivos no <summary> para melhor visualização:
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.
- 3d ago First seen · 471 lines · 3,406 tokens per session scan A a5495baaf3c0
markdown-organization is a cursor rule published in the GitHub repository Stramp/Lost-Mines-Phandelver (2 stars, last pushed 9mo ago), licensed MIT. It adds 3,406 tokens to every session, about $0.0170 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.