Borrowing it
Nothing to install: this file belongs to causify-ai/helpers. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/causify-ai/helpers/master/.claude/skills/todo.move_done/SKILL.mdgit clone --depth 1 https://github.com/causify-ai/helpersWrote 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/causify-ai/helpers/todo.move_done)<a href="https://agentmods.dev/skills/causify-ai/helpers/todo.move_done"><img src="https://agentmods.dev/badge/skills/causify-ai/helpers/todo.move_done/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/causify-ai/helpers/todo.move_done"><img src="https://agentmods.dev/badge/skills/causify-ai/helpers/todo.move_done.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.00026 | $0.00779 |
| Opus 5.5 | $0.00010 | $0.00312 |
| Sonnet 5.5 | $0.00005 | $0.00156 |
| Haiku 4.5 | $0.00003 | $0.00078 |
Grade A, and why
todo.move_done 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 1mo 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 — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Goal
- Find every top-level completed task (
### [x] <Title>) inai_task_queue.md - Move each one into
DONE.md, grouped under the same## <Topic>headers used in the# ALL TOPICSsection ofai_task_queue.md - Leave in-progress (
[ ],[.]) tasks and nested checklist items untouched
References
.claude/skills/todo.rules.md: defines the H1 stage / H2 topic / H3 task organization, and the rule thatDONE.mdreuses the# ALL TOPICSH2 headers fromai_task_queue.md
Workflow
Load the Conventions
- Read
.claude/skills/todo.rules.md - Read the
# ALL TOPICSsection ofai_task_queue.mdand extract the ordered list of## <Topic>headers (ignore// <group>comment lines, they are just visual grouping, not topics)
Find Completed Tasks
- In
ai_task_queue.md, find every H3 header that matches exactly### [x] <Title>- Do NOT move
### [ ],### [.], or any other marker - Do NOT move nested checklist items like
- [x] ...; those are subtask progress inside a task that is not itself done
- Do NOT move
- For each match, capture the full task block: the header line through everything up to (but not including) the next H1/H2/H3 header
Determine the Target Topic
- Find the nearest enclosing H2 header for the task in its source file
- If that H2 header name matches (case-insensitively) one of the ALL TOPICS entries, use it as the target topic
- Otherwise, infer the target topic from the task's content against the ALL TOPICS list
- If no ALL TOPICS entry is a plausible match, do not guess: list the task and ask
the user which topic to use, or whether to add a new topic to
# ALL TOPICS
Move the Tasks
- For each completed task, in source-file order:
- Remove the task block from its source file, closing the resulting blank line gap so surrounding spacing stays normal
- Append the task block, unchanged, under the matching
## <Topic>header inDONE.md- If
DONE.mdhas no header for that topic yet, create one, keeping the new headers in the same order as# ALL TOPICS - Keep multiple tasks for the same topic together under one header
- If
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.
- 1mo ago First seen · 73 lines · 26 tokens per session scan A 27a4ecd9b97a
todo.move_done is a skill published in the GitHub repository causify-ai/helpers (150 stars, last pushed today), licensed Apache-2.0. It adds 26 tokens to every session and 779 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-16.
Other skills, from other repositories
story-readiness
Is a story implementation-ready? Checks clear acceptance criteria, open questions, ADR refs. READY/NEEDS WORK/BLOCKED/NOT ASSESSED.
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.
ring:mapping-feature-relationships
Mapping how features relate and phasing the work: categorizing PRD features, grouping them into domains, charting cross-feature journeys, dependencies, and integration points, and defining the binding Phases that plan.md mirrors one-to-one at Gate 7. Gate 2 of ring:planning-large-features; runs after…
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…