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-task-authoringgit 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.00000 | $0.02426 |
| Opus 5 | $0.00000 | $0.01213 |
| Sonnet 5 | $0.00000 | $0.00485 |
| Haiku 4.5 | $0.00000 | $0.00243 |
Grade A, and why
taskplane-task-authoring 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 — 216 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Taskplane task authoring
Author runnable task packets for execution outside this chat. Packets are runner-agnostic file contracts: an executor with a fresh context should complete the work using only PROMPT, STATUS, listed docs, and the codebase.
Related: @taskplane-worker-cursor.mdc for implementing a packet in Cursor. Templates: @.cursor/rules/taskplane/prompt-template.md, @.cursor/rules/taskplane/status-template.md.
When this rule applies
Apply when the user asks to:
- Create, stage, queue, or plan tasks or batches
- Write or update
PROMPT.md,STATUS.md, or task-areaCONTEXT.md - Break a feature or spec into orchestratable work items
Do not apply for implementation. If the user asks to implement, fix, or ship code for a feature, defer to @taskplane-worker-cursor.mdc unless they also want new packets authored in the same turn—then author first, implement only if explicitly requested after.
If intent is ambiguous (create tasks vs implement now), ask once.
Orchestration artifacts vs repo docs
PROMPT.md, STATUS.md, and area CONTEXT.md under a tasks root are orchestration artifacts, not unsolicited documentation. Creating them when the user requests task work is allowed. See documentation-policy.mdc (Taskplane task packets exception).
Do not create unsolicited README files, change summaries, or PR writeups unless asked.
Packet layout
{tasks-root}/{PREFIX-###-slug}/
├── PROMPT.md # Definition (immutable above --- divider)
├── STATUS.md # Execution memory (mirrors PROMPT steps)
├── .reviews/ # Runtime — do not create at author time
└── .DONE # Runtime — do not create at author time
Optional at area level:
{tasks-root}/CONTEXT.md # Next Task ID, domain state, tech-debt backlog
Folder naming: PREFIX-###-short-slug (e.g. AUTH-014-add-role-checks).
Before you write
- Locate tasks root — Common defaults:
taskplane-tasks/,docs/task-management/. Read project config if present (task areas: path, prefix, context file; reference docs; test commands; standards paths; protected docs; never-load list). If unknown, ask the user for tasks-root, ID prefix, and full test command. - Read area
CONTEXT.md— UseNext Task IDfor the new task; you will increment it in the same edit pass. - Pick the area — Match task domain to the area that owns the primary files being changed. If multiple areas exist and scope is unclear, ask.
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 · 216 lines · 0 tokens per session scan A c6c866098dcc
taskplane-task-authoring is a cursor rule published in the GitHub repository beettlle/pi-spine (3 stars, last pushed 2d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,426 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
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.