documentation-reports

A set of project rules for creating reports, reviews, analyses, task records, test reports, and architecture documents in a specified folder.

In plain words
What is it for?
It tells the agent where to save code reviews, analyses, task reports, test reports, and architecture reports.
Why use it?
It keeps agent-created documentation in one predictable location instead of scattering it across the project.

Cursor rule for Cursor

Install

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.

agentmods
npx agentmods add rules/stramp/lost-mines-phandelver/documentation-reports
Clone the repo
git clone --depth 1 https://github.com/Stramp/Lost-Mines-Phandelver

Made for: Cursor.

Per session 1,435 This file is loaded in full into every session.
When invoked 1,435 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.01435 $0.01435
Opus 5 $0.00718 $0.00718
Sonnet 5 $0.00287 $0.00287
Haiku 4.5 $0.00144 $0.00144

Measured 2d ago against content hash af2bb972774d, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

documentation-reports 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 2d 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.

.cursor/rules/documentation-reports.mdc · 176 lines

How it starts

The opening of the file, as written. The whole thing — 176 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Documentation and Reports Rules

🚨 MANDATORY RULE - Reports Location 🚨

ALWAYS, ALWAYS, ALWAYS create reports, reviews, and analysis documents in the "00 - Executando" folder.

📁 Mandatory Location

ALL files created by agents in the following categories MUST be saved in:

F:\UNREAL GAME\minasphandelver\Documentacao\00 - Executando\relatorios\

📋 File Types That Must Follow This Rule

ALWAYS save in 00 - Executando/relatorios/ when creating:

  • Relatórios de Revisão (Code Reviews)

    • Exemplo: revisao-task-input-mvp-2025-01-25.md
    • Exemplo: revisao-arquitetura-componentes.md
  • Análises de Código (Code Analysis)

    • Exemplo: analise-performance-movement.md
    • Exemplo: analise-clean-code-compliance.md
  • Relatórios de Tarefas (Task Reports)

    • Exemplo: relatorio-implementacao-input-system.md
    • Exemplo: relatorio-refatoracao-helpers.md
  • Relatórios de Testes (Test Reports)

    • Exemplo: relatorio-cobertura-testes.md
    • Exemplo: relatorio-resultados-tdd.md
  • Relatórios de Arquitetura (Architecture Reports)

    • Exemplo: relatorio-analise-componentes.md
    • Exemplo: relatorio-proposta-refatoracao.md
  • Relatórios de Performance (Performance Reports)

    • Exemplo: relatorio-profiling-movement.md
    • Exemplo: relatorio-otimizacoes-recomendadas.md
  • Relatórios de Qualidade (Quality Reports)

    • Exemplo: relatorio-code-quality-review.md
    • Exemplo: relatorio-conformidade-clean-code.md
  • Relatórios de Debugging (Debugging Reports)

    • Exemplo: relatorio-investigacao-bug-movimento.md
    • Exemplo: relatorio-analise-crash.md
  • Relatórios de Refatoração (Refactoring Reports)

    • Exemplo: relatorio-refatoracao-helpers.md
    • Exemplo: relatorio-migracao-componentes.md
  • Relatórios de Integração (Integration Reports)

    • Exemplo: relatorio-integracao-enhanced-input.md
    • Exemplo: relatorio-integracao-gas.md

📝 Naming Convention

Read the full file on GitHub · 176 lines

Changes

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.

  1. 2d ago First seen · 176 lines · 1,435 tokens per session scan A af2bb972774d

Subscribe to this mod's changes

documentation-reports is a cursor rule published in the GitHub repository Stramp/Lost-Mines-Phandelver (2 stars, last pushed 9mo ago), licensed MIT. It adds 1,435 tokens to every session, about $0.0072 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.