plan-tasks

plan-tasks is a skill for Claude Code from motlin/claude-code-plugins. It costs 34 tokens per session (532 once invoked), scanned A, original, Apache-2.0.

A planning skill that converts a completed planning discussion into self-contained tasks in .llm/todo.md. It also archives the related plan so each task can point back to it.

In plain words
What is it for?
Use it at the end of planning, before coding starts, to create detailed tasks with files and implementation guidance.
Why use it?
It preserves decisions from planning and makes them usable as implementation tasks without requiring the agent to remember the conversation.

Skill for Claude Code

Written for Claude Code: ${CLAUDE_PLUGIN_ROOT} variable. Also seen: mentions Claude Code; mentions Codex.

Runs only inside its plugin — its command needs a path that Claude Code sets for a plugin’s own hooks and for nothing else. Install the plugin, not this.

Part of the markdown-tasks plugin — 8 skills shipped together

Good fit Use it at the end of planning, before coding starts, to create detailed tasks with files and implementation guidance.

Compare 6 skills from other repositories ↓
Install

Getting it into your agent

This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.

Claude Code
/plugin marketplace add motlin/claude-code-plugins
Claude Code
/plugin install markdown-tasks

Made for: Claude Code.

Or install markdown-tasks, the plugin that ships this one along with the rest of its 8 skills.

Wrote 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.

agentmods badge for plan-tasks

README.md
[![agentmods](https://agentmods.dev/badge/skills/motlin/claude-code-plugins/plan-tasks/github.svg)](https://agentmods.dev/skills/motlin/claude-code-plugins/plan-tasks)
Your own site
<a href="https://agentmods.dev/skills/motlin/claude-code-plugins/plan-tasks"><img src="https://agentmods.dev/badge/skills/motlin/claude-code-plugins/plan-tasks/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.

agentmods 80×15 button for plan-tasks

Your own site · 80×15
<a href="https://agentmods.dev/skills/motlin/claude-code-plugins/plan-tasks"><img src="https://agentmods.dev/badge/skills/motlin/claude-code-plugins/plan-tasks.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 34 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 532 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00034 $0.00532
Opus 5.5 $0.00014 $0.00213
Sonnet 5.5 $0.00007 $0.00106
Haiku 4.5 $0.00003 $0.00053

Measured 22d ago against content hash 896dea0b11c7, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

plan-tasks 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 22d 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/markdown-tasks/skills/plan-tasks/SKILL.md · 39 lines

How it starts

The opening of the file, as written. The whole thing — 39 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Plan Tasks

Turn the requirements, approaches, and implementation details discussed in this conversation into tasks appended to .llm/todo.md. Use this after planning and before any coding.

Use the markdown-tasks:tasks skill for task format and script path rules, including archiving any plan file under .llm/plans/ and putting its path in each task. <plugin-root> is ${CLAUDE_PLUGIN_ROOT} in Claude Code; in Codex, it is the plugin root that contains this skills/plan-tasks/SKILL.md file.

Each task must be readable on its own, from its - [ ] to the next one, and include:

  • Absolute file paths, never relative ones.
  • Exact class, function, or command names.
  • Existing patterns to follow, with analogies to similar code.
  • The specific methods or operations involved.
  • The module or package the work belongs to.
  • Dependencies and prerequisites.
  • The expected outcome.

Compose every task first, then add the batch in one shell command, chaining one call per task with && so concurrent sessions are unlikely to interleave their tasks:

python <plugin-root>/scripts/task_add.py .llm/todo.md "Task description
  Context line 1
  Context line 2" && \
python <plugin-root>/scripts/task_add.py .llm/todo.md "Another task
  Standalone context"

Example

- [ ] Create a new test class `SynchronizedBagTest` at `/workspace/project/unit-tests-thread-safety/src/test/java/com/example/collections/bag/mutable/SynchronizedBagTest.java` to test thread-safety of `com.example.collections.bag.mutable.SynchronizedBag`. Similar to how `SynchronizedMutableListTest` covers `SynchronizedMutableList`, this should extend `SynchronizedTestTrait` and implement test traits like `SynchronizedCollectionTestTrait`, `SynchronizedMutableIterableTestTrait`, and `SynchronizedRichIterableTestTrait`. The test should verify that all public methods of SynchronizedBag properly synchronize on the lock object using the `assertSynchronized()` method. Include tests for bag-specific methods like `addOccurrences()`, `removeOccurrences()`, `occurrencesOf()`, `forEachWithOccurrences()`, and `toMapOfItemToCount()`.

Read the full file on GitHub · 39 lines

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. 22d ago Changed · -9 lines 896dea0b11c7
  2. 1mo ago First seen · 48 lines · 34 tokens per session scan A c8836d325db1

Subscribe to this mod's changes

plan-tasks is a skill published in the GitHub repository motlin/claude-code-plugins (20 stars, last pushed yesterday), licensed Apache-2.0. It adds 34 tokens to every session and 532 once invoked, about $0.0001 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-09-19.

Related

Other skills, from other repositories