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/sweep-todos)<a href="https://agentmods.dev/skills/motlin/claude-code-plugins/sweep-todos"><img src="https://agentmods.dev/badge/skills/motlin/claude-code-plugins/sweep-todos/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/sweep-todos"><img src="https://agentmods.dev/badge/skills/motlin/claude-code-plugins/sweep-todos.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.00041 | $0.00289 |
| Opus 5.5 | $0.00016 | $0.00116 |
| Sonnet 5.5 | $0.00008 | $0.00058 |
| Haiku 4.5 | $0.00004 | $0.00029 |
Grade A, and why
sweep-todos 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.
What it actually says
Sweep TODOs
Turn every TODO comment in the codebase into a task in .llm/todo.md.
Use the markdown-tasks:tasks skill for task format and script path rules. <plugin-root> is ${CLAUDE_PLUGIN_ROOT} in Claude Code; in Codex, it is the plugin root that contains this skills/sweep-todos/SKILL.md file.
Search the codebase for every TODO and capture its file path, line number, and full text with comment markers (//, #, /* */) removed.
Compose all tasks first, then add the batch in one shell command, chaining one call per TODO with && so concurrent sessions are unlikely to interleave their tasks:
python <plugin-root>/scripts/task_add.py .llm/todo.md "Implement TODO from src/api/client.ts:87: Extract commonality in getRootNodes and getChildNodes" && \
python <plugin-root>/scripts/task_add.py .llm/todo.md "Implement TODO from test/utils.test.ts:103: Use deep object equality rather than loose assertions"
Report how many TODO tasks were added.
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 · -11 lines 0cb3a84b6105
- 1mo ago First seen · 33 lines · 41 tokens per session scan A 4285b3762146
sweep-todos is a skill published in the GitHub repository motlin/claude-code-plugins (20 stars, last pushed yesterday), licensed Apache-2.0. It adds 41 tokens to every session and 289 once invoked, about $0.0002 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.