taskplanner-dev

Instructions for contributing to TaskPlanner, a TypeScript VS Code extension that tracks work in Git-managed Markdown files.

In plain words
What is it for?
Choosing the next task, planning and implementing changes, running tests and code checks, formatting files, and moving tasks between workflow files.
Why use it?
It explains the repository layout, development commands, and the required process for moving tasks from the backlog through completion.

Cursor rule for Cursor

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-dev
Clone the repo
git clone --depth 1 https://github.com/smekai/taskplanner

Made for: Cursor.

Per session 536 This file is loaded in full into every session.
When invoked 536 The same file — it is already loaded in full.
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.00536 $0.00536
Opus 5 $0.00268 $0.00268
Sonnet 5 $0.00107 $0.00107
Haiku 4.5 $0.00054 $0.00054

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

Security

Grade A, and why

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

.cursor/rules/taskplanner-dev.mdc · 45 lines

What it actually says

TaskPlanner (refined)

This repo provides markdown-based task tracking stored as .md files under .tasks/ (git-tracked and AI-friendly).

Tech stack

  • TypeScript (strict mode) + esbuild bundling
  • Unit tests: Vitest (npm test)
  • Lint: ESLint (npm run lint)
  • Format: Prettier (npm run format)

Code layout

  • src/core/: pure logic, no vscode dependency
  • src/extension/: VS Code extension shell (commands, views, providers, watchers)
  • src/test/core/: Vitest unit tests for core logic
  • src/test/extension/: integration tests (via @vscode/test-cli)

Task workflow for agents (task-agent instructions)

When implementing tasks, follow the task conventions used by TaskPlanner:

  • Tasks live in .tasks/*.md as ## TASK-###: ... sections
  • Tasks are separated by ---
  • Agents should:
    1. Pick the task from NEXT.md or BACKLOG.md (highest priority first)
    2. Move it to IN_PROGRESS.md by removing it from the source file and pasting it into IN_PROGRESS.md
    3. Add a ### Plan subsection under the task heading when aiPlanRequired is enabled
    4. Implement the task
    5. Move it to DONE.md when complete

When asked to create a new task:

  1. Read .tasks/config.json to get nextId and idPrefix
  2. Generate the ID: {idPrefix}-{nextId padded to 3 digits} (e.g. TASK-015)
  3. Increment nextId in config.json and save
  4. Write the task into BACKLOG.md (or the file the user specifies), respecting insertPosition (top/bottom, after the # Heading line)
  5. Use the standard format: ## TASK-###: Title, **Priority:**, optional **Tags:**, **Updated:**, description, and --- separator

Note: the extension command TaskPlanner: Initialize AI Instructions updates root .cursorrules and CLAUDE.md (idempotent via markers). This .cursor/rules directory is separate and intended for persistent developer guidance.

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 · 45 lines · 536 tokens per session scan A 842d58ba21b1

Subscribe to this mod's changes

taskplanner-dev is a cursor rule published in the GitHub repository smekai/taskplanner (19 stars, last pushed 4d ago), licensed MIT. It adds 536 tokens to every session, about $0.0027 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-30.