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/hlalljie/agent-workflow-presetsWrote 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/hlalljie/agent-workflow-presets/task-scope)<a href="https://agentmods.dev/rules/hlalljie/agent-workflow-presets/task-scope"><img src="https://agentmods.dev/badge/rules/hlalljie/agent-workflow-presets/task-scope/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/hlalljie/agent-workflow-presets/task-scope"><img src="https://agentmods.dev/badge/rules/hlalljie/agent-workflow-presets/task-scope.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.00476 | $0.00476 |
| Opus 5.5 | $0.00190 | $0.00190 |
| Sonnet 5.5 | $0.00095 | $0.00095 |
| Haiku 4.5 | $0.00048 | $0.00048 |
Grade A, and why
task-scope 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
One task per message (default)
A task is one numbered block in a plan task file, e.g. ### Task N: … under .cursor/plans/**/tasks/*.md.
- Implement at most one such task per user message unless a skill the user invoked or a user instructions explicitly directs otherwise (e.g. run-task-loop — work through tasks in order in that session until done, blocked, or that skill's handoff).
- Multi-task only if the same message explicitly names more than one task number (e.g. "Task 3 and 5", "do 3, 5", "tasks 2–4").
- Or the task file's first line (the
# …title line) contains the literal substringbatchable: true. Then the user must still say they want batching in that message; the flag only allows it, it does not auto-batch.
Forbidden expansions
Without a new message that names another task number, do not:
- Implement the next task because tests, MSW, build, or "verification" need it.
- Add "small" wrappers, clients, or handlers for a different task section.
- Mark additional checkboxes complete in the plan for work you were not asked to do.
If work truly depends on another task, state the dependency in prose and stop. Do not implement the dependency unless the user then names that task.
Discussion is not implementation
If the user is venting, reviewing a mistake, asking why, or debating process: no repo edits unless they give a separate, explicit implement instruction (e.g. "apply that patch", "revert task 4").
Ordering
If the user references a task file but no task number: do not guess. Ask which Task N to run (one line).
To author a new task file from a plan phase, use the create-task-list skill.
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 · 33 lines · 476 tokens per session scan A 624e8e5ff4a3
task-scope is a cursor rule published in the GitHub repository hlalljie/agent-workflow-presets (2 stars, last pushed 8d ago), licensed MIT. It adds 476 tokens to every session, about $0.0019 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
incremental-verify
Verify each behavior before building the next. One test, one implementation, one commit. No bulk-writing tests for behavior that does not yet exist.
context-discipline
Manage AI context window efficiently - read before write, no re-reads, tool-call budgets, one-pass discipline.
x402-coding
@dexterai/x402 SDK conventions and hosted-only OpenDexter tool usage.
pn-rust-backend
Rust backend style, env, and error handling. Use for API and server code (Actix-web, Axum).
pn-visual-indicator
Tag every pnCore-touched assistant response with a context tag plus 🔺 (red triangle emoji) so the response is visible at a glance in Cursor's chat UI.
pn-tool-risk-policy
MCP tool risk tiers, HITL gates, and when to use approvalcheckpoint and gatelogappend. Use for safety reviews and workflow audits.