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/smekai/taskplannerWrote 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/smekai/taskplanner/taskplanner-dev)<a href="https://agentmods.dev/rules/smekai/taskplanner/taskplanner-dev"><img src="https://agentmods.dev/badge/rules/smekai/taskplanner/taskplanner-dev/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/smekai/taskplanner/taskplanner-dev"><img src="https://agentmods.dev/badge/rules/smekai/taskplanner/taskplanner-dev.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.00534 | $0.00534 |
| Opus 5.5 | $0.00214 | $0.00214 |
| Sonnet 5.5 | $0.00107 | $0.00107 |
| Haiku 4.5 | $0.00053 | $0.00053 |
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.
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, novscodedependencysrc/extension/: VS Code extension shell (commands, views, providers, watchers)test/core/: Vitest unit tests for core logictest/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/*.mdas## TASK-###: ...sections - Tasks are separated by
--- - Agents should:
- Pick the task from
NEXT.mdorBACKLOG.md(highest priority first) - Move it to
IN_PROGRESS.mdby removing it from the source file and pasting it intoIN_PROGRESS.md - Add a
### Plansubsection under the task heading whenaiPlanRequiredis enabled - Implement the task
- Move it to
DONE.mdwhen complete
- Pick the task from
When asked to create a new task:
- Read
.tasks/config.jsonto getnextIdandidPrefix - Generate the ID:
{idPrefix}-{nextId padded to 3 digits}(e.g.TASK-015) - Increment
nextIdinconfig.jsonand save - Write the task into
BACKLOG.md(or the file the user specifies), respectinginsertPosition(top/bottom, after the# Headingline) - 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.
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 Changed · -2 tokens per session 93124c376d46
- 1mo ago First seen · 45 lines · 536 tokens per session scan A 842d58ba21b1
taskplanner-dev is a cursor rule published in the GitHub repository smekai/taskplanner (23 stars, last pushed 3d ago), licensed MIT. It adds 534 tokens to every session, about $0.0021 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-30.
Other cursor rules, from other repositories
rebase-only-merged-agents
When rebasing after a merge, only rebase the agents whose branches you just merged. Do not rebase agents that are still running.
iris
GitHub operations specialist — branches, pull requests, issues, releases, tags. Called by zeus after review. Never pushes or merges without explicit human approval. Integrates with VS Code GitHub Pull Requests extension.
git-workflow
Rules for git operations, commit strategy, and GitHub CLI usage.
release-checklist
What to update with each code change or version release.
git-workflow
Git commit format and PR process - conventional commits.
branching-merging-strategy
This is a set of instructions to the AI Assistant for branching and merging strategy.