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/budagov-lab/DreamTeamWrote 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/budagov-lab/dreamteam/task-execution)<a href="https://agentmods.dev/rules/budagov-lab/dreamteam/task-execution"><img src="https://agentmods.dev/badge/rules/budagov-lab/dreamteam/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/budagov-lab/dreamteam/task-execution"><img src="https://agentmods.dev/badge/rules/budagov-lab/dreamteam/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.00000 | $0.00277 |
| Opus 5.5 | $0.00000 | $0.00111 |
| Sonnet 5.5 | $0.00000 | $0.00055 |
| Haiku 4.5 | $0.00000 | $0.00028 |
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.
What it actually says
Task Execution Rules
When Working on Tasks
- Read the full task file before starting.
- Verify all dependencies are
donein the database. - Task is set to
in_progressbyrun-nextwhen Orchestrator assigns it. - Implement the changes specified in the task.
- Run tests and fix any failures.
- Do NOT run update-task done — Orchestrator runs it after Reviewer approval and Git-Ops commit. Developer only delivers code.
- Run
dreamteam verify-tasksperiodically to check DB/file consistency.
Task File Structure
Each task file must contain:
id— Unique identifier (e.g. T001)title— Short descriptionstatus— todo | in_progress | done | blocked | deprecatedsort_order— optional, integer (lower = earlier in queue)priority— Integer (higher = more urgent)dependencies— List of task IDs that must be done firstowner— Optional agent identifier
Blocked Tasks
If a task is blocked, document the reason in the task file and ensure the database status is blocked.
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 · 34 lines · 0 tokens per session scan A 05907c5ff018
task-execution is a cursor rule published in the GitHub repository budagov-lab/DreamTeam (1 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 277 tokens. 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
nextjs
Rules for Next.js projects (App Router and Pages Router).
php
Rules applied when working in PHP files (incl. Laravel, Symfony, WordPress).
cursorrules
40 lines, or explicitly requested.
shell
Rules for shell scripts (bash, zsh, sh, PowerShell).
tests
Rules for test files — keep tests lean and pattern-matched.
vue
Rules for Vue (2 and 3) single-file components.