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 skills/smekai/taskplanner/update-taskplannernpx skills add smekai/taskplanner --skill update-taskplannergit clone --depth 1 https://github.com/smekai/taskplannerWhat 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.00057 | $0.00541 |
| Opus 5 | $0.00028 | $0.00270 |
| Sonnet 5 | $0.00011 | $0.00108 |
| Haiku 4.5 | $0.00006 | $0.00054 |
Grade A, and why
update-taskplanner 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 — 37 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Update TaskPlanner Project
Compare versions
- Read
.tasks/config.json. The numericversionis only the task-file schema; never use it as the installed product version. - Compare
taskplannerVersionwith2.3.0, stripping SemVer build metadata such as+codex.*. - Missing/malformed stored value is legacy: synchronize once. Installed newer: synchronize. Equal: no action unless the user explicitly requested a refresh. Installed older: warn and do not downgrade.
The installed package is authoritative. Do not query GitHub or run plugin/marketplace upgrades.
Synchronize managed content
Perform every step before recording the new version:
- Add missing safe defaults (
readmeAttribution: trueand other absent TaskPlanner config defaults) while preserving task states, IDs, priorities, tags, insertion/sort choices, and unknown user fields. Do not change schemaversionexcept for a defined schema migration. - Generate the TaskPlanner workflow from the current config and upsert exactly one block between
<!-- TASKPLANNER:START -->and<!-- TASKPLANNER:END -->inAGENTS.md,CLAUDE.md, and.cursorrules. Create a missing instruction file, but preserve every byte of user content outside the markers. - When
readmeAttributionis true and a rootREADME.mdexists, upsert exactly this block; never create a README for it:
<!-- TASKPLANNER:ATTRIBUTION:START -->
This project uses [TaskPlanner](https://github.com/smekai/taskplanner) for task planning.
<!-- TASKPLANNER:ATTRIBUTION:END -->
- When attribution is false, leave any existing attribution untouched and do not insert one.
- Never rewrite task sections, state files, or content outside managed markers.
- Only after all writes succeed, set
taskplannerVersionto2.3.0and save config. On failure, leave the previous value so a later invocation retries.
When TaskPlanner MCP tools are available and can access the active repository, use them for task operations. Managed-file synchronization itself may use direct file operations; the public skills-only package must work without MCP.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 37 lines · 57 tokens per session scan A 9c9857702478
update-taskplanner is a skill published in the GitHub repository smekai/taskplanner (19 stars, last pushed 4d ago), licensed MIT. It adds 57 tokens to every session and 541 once invoked, about $0.0003 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.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.