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/beettlle/pi-spine/taskplane-worker-cursorgit clone --depth 1 https://github.com/beettlle/pi-spineWhat 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.00048 | $0.01449 |
| Opus 5 | $0.00024 | $0.00724 |
| Sonnet 5 | $0.00010 | $0.00290 |
| Haiku 4.5 | $0.00005 | $0.00145 |
Grade A, and why
taskplane-worker-cursor 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.
How it starts
The opening of the file, as written. The whole thing — 115 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Taskplane worker (Cursor)
Execute work defined in a task packet (PROMPT.md + STATUS.md). The PROMPT is the contract; STATUS is your memory between turns. Stay within scope; verify before claiming done.
Related: @taskplane-task-authoring.mdc for creating packets. Universal verification rules: general-llm-anti-patterns.mdc sections 3.8 and 3.9.
Manual activation: @taskplane-worker-cursor in chat when the agent does not auto-select this rule.
When this rule applies
Apply when the user:
- References a task ID (
PREFIX-###) or@PROMPT.md - Asks to execute, implement, or continue a staged task
- Works from a task folder with active PROMPT/STATUS
Do not apply when the user only wants new packets authored—use @taskplane-task-authoring.mdc.
If the user authored packets for an external runner and did not ask you to implement in Cursor, do not start coding unless they explicitly request it.
Startup (every session)
- Read full
PROMPT.md— Mission, Dependencies, Context to Read First, File Scope, Do NOT, Testing step, Completion Criteria, Review Level. - Read
STATUS.md— Current step, first unchecked checkbox in scope. - Load only docs listed in Context to Read First (plus files needed for the current checkbox).
- Confirm dependencies are satisfied (prior tasks merged, external prerequisites met). If blocked, say so and stop.
Do not load the entire codebase when PROMPT lists specific paths.
Execution loop
- One checkbox at a time within the current step (or current segment in multi-repo steps).
- Implement only within File Scope.
- Update STATUS — Mark
- [x]when the outcome is truly done; update step status if your workflow uses it. - Tests — At step boundaries, run targeted tests when PROMPT implies them. On the dedicated Testing step, run the exact command(s) written in PROMPT.
- Commits — Use the task ID prefix from PROMPT's Git Commit Convention at step boundaries when committing (not necessarily after every checkbox).
- Verification claims — Show test/build output or state verification pending. Never claim tests pass or builds succeed without evidence.
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.
- 2d ago First seen · 115 lines · 48 tokens per session scan A 4433a0bc9b68
taskplane-worker-cursor is a cursor rule published in the GitHub repository beettlle/pi-spine (3 stars, last pushed 2d ago), licensed MIT. It adds 48 tokens to every session and 1,449 once invoked, about $0.0002 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
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
cli-error-handling
CLI command error handling patterns.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.
family-instance-domain-actions
Family instance domain action implementation patterns.