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/task-start-checklistgit 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/task-start-checklist)<a href="https://agentmods.dev/rules/stramp/lost-mines-phandelver/task-start-checklist"><img src="https://agentmods.dev/badge/rules/stramp/lost-mines-phandelver/task-start-checklist.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.03299 | $0.03299 |
| Opus 5 | $0.01649 | $0.01649 |
| Sonnet 5 | $0.00660 | $0.00660 |
| Haiku 4.5 | $0.00330 | $0.00330 |
Grade A, and why
task-start-checklist 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 — 420 lines — stays where its author put it; the contents beside it link to each section on GitHub.
📋 Roteiro de Início de Nova Task
🎯 Objetivo
Este documento define o roteiro completo e obrigatório para iniciar uma nova task, garantindo que a branch seja criada corretamente, conectada com a issue no GitHub, e que o desenvolvimento siga TDD desde o início.
✅ Checklist de Início de Task
1. Verificações Pré-Início
-
Task está clara e bem definida?
- Li a documentação da task (arquivo
.mdem04-Planning/ciclos/) - Entendi o que precisa ser feito
- Verifiquei dependências (outras tasks que precisam estar completas)
- Task tem issue criada no GitHub?
- Li a documentação da task (arquivo
-
Ambiente está pronto?
- Estou na branch
main(ou branch base correta) - Branch local está atualizada (
git pull origin main) - Working tree está limpo (
git statuslimpo) - Projeto compila sem erros
- Estou na branch
2. Criar Branch e Conectar com Issue
- Criar branch conectada com issue
- Usar script
create-task-branch.ps1 - Script cria branch no formato:
feat/issue-<NUMBER>__<ciclo>-<nome> - Script conecta branch com issue no GitHub
- Script move issue automaticamente para "In Progress"
- Usar script
Comando:
cd "F:\UNREAL GAME\MyProject2"
.\scripts\github\create-task-branch.ps1 <arquivo-task.md>
Exemplo:
.\scripts\github\create-task-branch.ps1 "fase-1\03-criacao-personagem\03-05-ac-base-mvp.md"
O que o script faz:
- Lê o arquivo
.mde extrai o título - Busca a issue no GitHub pelo título
- Cria branch no formato:
feat/issue-<NUMBER>__<ciclo>-<nome> - Faz checkout automaticamente
- Conecta branch com issue no GitHub
- Tenta mover card do projeto para "In Progress"
- Verificar que branch foi criada corretamente
- Branch existe localmente?
- Estou na branch correta?
- Branch está conectada com issue no GitHub?
- Issue foi movida para "In Progress"?
Comandos de verificação:
# Verificar branch atual
git branch --show-current
# Verificar issue conectada
gh issue view <NUMBER> --json number,title,state,url
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 · 420 lines · 3,299 tokens per session scan A e228a63e2cbf
task-start-checklist is a cursor rule published in the GitHub repository Stramp/Lost-Mines-Phandelver (2 stars, last pushed 9mo ago), licensed MIT. It adds 3,299 tokens to every session, about $0.0165 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
development-workflow
AAMAD modular development workflow for context-aware agent coordination.
feedback-enhanced
Enhanced feedback mechanism with 1-hour timeout - 增强反馈机制，1小时超时.
project-onboarding-rule
Automatically onboards existing projects into the AI-driven development workflow.
linear-in-review
After finishing a Linear issue, set its status to In Review (never Done).
sprint-planning
BMAD BMM Agent: sprint-planning.
generate-tasks
Understanding our task list for our project or how to make one from a PRD.