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.
/plugin marketplace add motlin/claude-code-plugins/plugin install markdown-tasksWrote 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/skills/motlin/claude-code-plugins/plan-tasks)<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.
<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>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.00034 | $0.00532 |
| Opus 5.5 | $0.00014 | $0.00213 |
| Sonnet 5.5 | $0.00007 | $0.00106 |
| Haiku 4.5 | $0.00003 | $0.00053 |
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.
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()`.
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.
- 22d ago Changed · -9 lines 896dea0b11c7
- 1mo ago First seen · 48 lines · 34 tokens per session scan A c8836d325db1
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.
Other skills, from other repositories
story-readiness
Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
handle-linkedin-connection-request-signal
Use this skill when someone sends a team member an inbound LinkedIn connection request. An inbound request is a deliberate, ACTIVE first-party intent signal — meaningfully stronger than a passive profile view — and it deserves different scoring rules. The skill resolves and enriches the requester, gates them through…
remove
Remove a deployed framework or addon from the current workspace.