todo.move_to_reorg

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

A task-organising tool that moves tasks from a reorganisation section into the correct stage and topic in a Markdown task queue.

In plain words
What is it for?
Use it to sort tasks in `ai_task_queue.md` by stage and topic, using an optional priority tag.
Why use it?
It prevents tasks from staying in a catch-all section and requires confirmation before changing their locations.

Skill for Claude Code

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

Good fit Use it to sort tasks in ai_task_queue.md by stage and topic, using an optional priority tag.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/gpsaggese/helpers/todo.move_to_reorg
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_to_reorg
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_to_reorg

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/gpsaggese/helpers/todo.move_to_reorg"><img src="https://agentmods.dev/badge/skills/gpsaggese/helpers/todo.move_to_reorg.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 33 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,266 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.00033 $0.01266
Opus 5.5 $0.00013 $0.00506
Sonnet 5.5 $0.00007 $0.00253
Haiku 4.5 $0.00003 $0.00127

Measured yesterday against content hash 2489f08d07c6, 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_to_reorg 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_to_reorg/SKILL.md · 115 lines

How it starts

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

Goal

  • Find every H3 task under # TO REORG in ai_task_queue.md
  • For each task, find its target H1 stage (from an optional - Priority: <Stage> line in the body, default # BACKLOG) and its target H2 topic (from the # ALL TOPICS list)
  • Get explicit user confirmation of all proposed moves before changing the file
  • Move each confirmed task under ## <Topic> (<Stage>) in its H1 section, stripping the used Priority: line
  • Remove the # TO REORG header once it has no tasks left

References

  • .claude/skills/todo.rules.md: defines the H1 stage / H2 topic / H3 task organization, the ## <Topic> (<Stage>) header convention, and the # ALL TOPICS master list

Workflow

Load the Conventions

  • Read .claude/skills/todo.rules.md
  • Record the ordered ## <Topic> headers in ai_task_queue.md's # ALL TOPICS section. Ignore // <group> comment lines: they are visual grouping, not topics
  • Record the H1 stage headers in the file (e.g. # IN PROGRESS, # BACKLOG - HIGH PRIORITY, # BACKLOG, # ICEBOX). These are the only valid move targets

Find the Tasks to Reorg

  • Find every H3 header under # TO REORG
  • Capture each full task block: the header line through everything before the next H1/H2/H3 header

Determine the Target H1 Stage

  • Find a - Priority: <Stage> line anywhere in the task body
    • Match <Stage> case-insensitively to an existing H1 stage (e.g. Icebox -> # ICEBOX, High Priority -> # BACKLOG - HIGH PRIORITY, Backlog -> # BACKLOG, In Progress -> # IN PROGRESS)
    • If <Stage> does not clearly match an H1, do not guess. List the task and ask the user which H1 stage to use
  • If there is no - Priority: line, propose # BACKLOG as the default. This is only a proposal and can be overridden at confirmation

Determine the Target H2 Topic

  • Match the task content against the # ALL TOPICS list, the same way todo.move_done infers a topic
  • If no entry is a plausible match, do not guess. List the task and ask whether to use the closest existing topic or add a new one to # ALL TOPICS

Read the full file on GitHub · 115 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 · 115 lines · 33 tokens per session scan A 2489f08d07c6

Subscribe to this mod's changes

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

Related

todo.move_to_reorg compared with skills from other repositories

todo.move_to_reorg next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
todo.move_to_reorggpsaggese/helpersSkill158todayApache-2.0A33Claude 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