agentmods.dev

todo.move_done

todo.move_done is a skill for Claude Code from gpsaggese/helpers. It costs 26 tokens per session (679 once invoked), scanned A, original, Apache-2.0.

A task-management routine that moves finished top-level tasks from one Markdown queue file into a separate completed-work file, grouped by topic.

In plain words
What is it for?
Use it to organize completed tasks in `DONE.md` while preserving the topic structure from `ai_task_queue.md`.
Why use it?
It keeps the active queue focused without losing a record of completed work. It also avoids moving unfinished tasks or checklist items by mistake.

Skill for Claude Code

Written for Claude Code: installed under .claude/. Also seen: reads .claude/ paths.

not rated 158repo +1 today A scan 26 tokens original Apache-2.0

Good fit Use it to organize completed tasks in DONE.md while preserving the topic structure from ai_task_queue.md.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/gpsaggese/helpers/todo.move_done
View source ↗ gpsaggese/helpers
Install

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.

Any agent
npx skills add gpsaggese/helpers --skill todo.move_done
Clone the repo
git clone --depth 1 https://github.com/gpsaggese/helpers

Made for: Claude Code.

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 todo.move_done

README.md
[![agentmods](https://agentmods.dev/badge/skills/gpsaggese/helpers/todo.move_done/github.svg)](https://agentmods.dev/skills/gpsaggese/helpers/todo.move_done)
Your own site
<a href="https://agentmods.dev/skills/gpsaggese/helpers/todo.move_done"><img src="https://agentmods.dev/badge/skills/gpsaggese/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.

agentmods 80×15 button for todo.move_done

Your own site · 80×15
<a href="https://agentmods.dev/skills/gpsaggese/helpers/todo.move_done"><img src="https://agentmods.dev/badge/skills/gpsaggese/helpers/todo.move_done.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 26 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 679 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.00026 $0.00679
Opus 5.5 $0.00010 $0.00272
Sonnet 5.5 $0.00005 $0.00136
Haiku 4.5 $0.00003 $0.00068

Measured yesterday against content hash b11b7111af3e, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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

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.

.claude/skills/todo.move_done/SKILL.md · 67 lines

How it starts

The opening of the file, as written. The whole thing — 67 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>) in ai_task_queue.md
  • Move each into DONE.md, under the same ## <Topic> headers as the # ALL TOPICS section of ai_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 that DONE.md reuses the # ALL TOPICS H2 headers

Workflow

Load the Conventions

  • Read .claude/skills/todo.rules.md
  • Read # ALL TOPICS in ai_task_queue.md and extract the ordered ## <Topic> headers (ignore // <group> comment lines: they are visual grouping, not topics)

Find Completed Tasks

  • Find every H3 header matching exactly ### [x] <Title> in ai_task_queue.md
    • Do NOT move ### [ ], ### [.], or other markers
    • Do NOT move nested items like - [x] ...: they are subtask progress in a task that is not done
  • Capture each full task block: the header line through the line before the next H1/H2/H3 header

Determine the Target Topic

  • Use the nearest enclosing H2 header in the source file if it matches an ALL TOPICS entry (case-insensitive)
  • Otherwise infer the topic from the task's content against the ALL TOPICS list
  • If no 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 block from its source file, closing the blank line gap so spacing stays normal
    • Append the block, unchanged, under the matching ## <Topic> header in DONE.md
      • If DONE.md lacks that header, create it, keeping headers in # ALL TOPICS order
      • Keep tasks of the same topic together under one header

Report

  • List each moved task as <Title> (<source file>) -> ## <Topic>
  • List separately any task that could not be confidently mapped to a topic, and why

Verification

Read the full file on GitHub · 67 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. yesterday First seen · 67 lines · 26 tokens per session scan A b11b7111af3e

Subscribe to this mod's changes

todo.move_done is a skill published in the GitHub repository gpsaggese/helpers (158 stars, last pushed today), licensed Apache-2.0. It adds 26 tokens to every session and 679 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-11-06.

Project management
Related

todo.move_done compared with skills from other repositories

todo.move_done next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
todo.move_donegpsaggese/helpersSkill158todayApache-2.0A26Claude Code
imagegenopenai/codexSkill134ktodayApache-2.0A113Codex
local-ai-agentsmicrosoft/ai-agents-for-beginnersSkill79ktodayMITA200Claude Code, Codex
playwright-climicrosoft/playwrightSkill99ktodayApache-2.0A19Claude Code
systematic-debuggingobra/superpowersSkill314k3d agoMITA21Claude Code
next-cache-components-adoptionvercel/next.jsSkill143ktodayMITA95Claude Code
chat-pet-sprite-creationmicrosoft/vscodeSkill195ktodayMITA53Claude Code, Codex