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/task-execution)<a href="https://agentmods.dev/rules/stramp/lost-mines-phandelver/task-execution"><img src="https://agentmods.dev/badge/rules/stramp/lost-mines-phandelver/task-execution/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/task-execution"><img src="https://agentmods.dev/badge/rules/stramp/lost-mines-phandelver/task-execution.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.01894 | $0.01894 |
| Opus 5.5 | $0.00758 | $0.00758 |
| Sonnet 5.5 | $0.00379 | $0.00379 |
| Haiku 4.5 | $0.00189 | $0.00189 |
Grade A, and why
task-execution 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 — 275 lines — stays where its author put it; the contents beside it link to each section on GitHub.
🎯 Task Execution Rules
🚨 MAIN RULE - INTEGRITY AND MODULARITY 🚨
ALWAYS follow these rules when executing any task:
- ✅ TDD mandatory: All tasks must be tested and all tests must pass
- ✅ Modularity: Focus only on task integrity while always being modular
- ✅ GitHub Integration: Move task from TODO to In Progress on GitHub
- ✅ Branch Creation: Always create branch to start a task
- ✅ Auto Status Update: When adding branch to issue, automatically move to In Progress
📋 Task Execution Workflow
1. Task Start
ALWAYS follow this sequence:
-
Create branch for the task
git checkout -b feature/task-XX-task-name -
Add branch to issue on GitHub
- Use script
create-task-branch.ps1or equivalent - Script must automatically move issue to "In Progress"
- Use script
-
Write tests FIRST (TDD - Red)
- Follow rule
test-driven-development-core.mdc - Tests must fail initially (Red)
- Follow rule
-
Implement minimal functionality (TDD - Green)
- Make tests pass with minimal implementation
-
Refactor safely (TDD - Refactor)
- Improve code while keeping tests green
2. During Development
ALWAYS maintain:
- ✅ Modularity: Each function/class with single responsibility
- ✅ Tests passing: All tests must pass before commit
- ✅ Clean Code: Follow
clean-code-mandatory.mdc - ✅ Architecture: Respect
project-architecture.mdc
NEVER:
- ❌ Commit code without tests
- ❌ Commit code with failing tests
- ❌ Create non-modular code
- ❌ Violate Clean Code principles
3. Task Completion
ALWAYS verify before marking as completed:
- All tests pass?
- Code follows Clean Code?
- Code is modular?
- Architecture respected?
- Documentation updated (if necessary)?
- Branch added to issue?
- Issue moved to "In Progress" (or "Done" if completed)?
🔄 Integração com GitHub
Branch Creation Script
ALWAYS usar script que:
- Cria branch localmente
- Adiciona branch na issue do GitHub
- Automaticamente move issue para "In Progress"
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 · 275 lines · 1,894 tokens per session scan A 7179f834f55d
task-execution is a cursor rule published in the GitHub repository Stramp/Lost-Mines-Phandelver (2 stars, last pushed 10mo ago), licensed MIT. It adds 1,894 tokens to every session, about $0.0076 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
workflow
Development workflow and commit practices.
practices
Engineering practices and definition of done for agent work.
cmd-build
Implement the next task incrementally — build, test, verify, commit.
development-workflow
Use pnpm as the package manager (not npm or yarn).
mcpnuke-tests
Test conventions for mcpnuke — enforces TDD workflow.
roslyn-mcp-version-bump
Auto-bump Version after successful MCP self-build and reload.