taskplanner-workflow

Rules for writing and editing task records stored in .tasks/ files. They define the required headings, priorities, separators, and optional task details.

In plain words
What is it for?
Creating, editing, and moving tasks while preserving IDs, priorities, metadata, plans, and section separators.
Why use it?
They prevent task files from losing their expected structure or changing task identifiers accidentally.

Cursor rule

Install

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.

agentmods
npx agentmods add rules/smekai/taskplanner/taskplanner-workflow
Clone the repo
git clone --depth 1 https://github.com/smekai/taskplanner
Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 161 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.00161
Opus 5 $0.00000 $0.00081
Sonnet 5 $0.00000 $0.00032
Haiku 4.5 $0.00000 $0.00016

Measured 2d ago against content hash 301ec8caf246, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

taskplanner-workflow 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.

plugins/taskplanner/rules/taskplanner-workflow.mdc · 17 lines

What it actually says

When editing files in .tasks/:

  • Each task is a ## TASK-###: Title heading section
  • Tasks are separated by --- on its own line
  • Priority is required: **Priority:** P0 through P4
  • Optional metadata: **Tags:**, **Assignee:**, **Updated:**, **Epic:**
  • A ### Plan subsection can appear under the task heading
  • Do NOT change task IDs
  • Do NOT remove the --- separators
  • When moving a task between files, remove it entirely from the source (including trailing ---)
Changes

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.

  1. 2d ago First seen · 17 lines · 0 tokens per session scan A 301ec8caf246

Subscribe to this mod's changes

taskplanner-workflow is a cursor rule published in the GitHub repository smekai/taskplanner (19 stars, last pushed 4d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 161 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-30.