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.
npx skills add gpsaggese/helpers --skill todo.move_to_reorggit clone --depth 1 https://github.com/gpsaggese/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/gpsaggese/helpers/todo.move_to_reorg)<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.
<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>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.00033 | $0.01266 |
| Opus 5.5 | $0.00013 | $0.00506 |
| Sonnet 5.5 | $0.00007 | $0.00253 |
| Haiku 4.5 | $0.00003 | $0.00127 |
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.
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 REORGinai_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 TOPICSlist) - 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 usedPriority:line - Remove the
# TO REORGheader 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 TOPICSmaster list
Workflow
Load the Conventions
- Read
.claude/skills/todo.rules.md - Record the ordered
## <Topic>headers inai_task_queue.md's# ALL TOPICSsection. 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
- Match
- If there is no
- Priority:line, propose# BACKLOGas 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 TOPICSlist, the same waytodo.move_doneinfers 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
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.
- yesterday First seen · 115 lines · 33 tokens per session scan A 2489f08d07c6
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.
todo.move_to_reorg compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| todo.move_to_reorggpsaggese/helpers | Skill | 158 | today | Apache-2.0 | A | 33 | Claude Code |
| imagegenopenai/codex | Skill | 134k | today | Apache-2.0 | A | 113 | Codex |
| local-ai-agentsmicrosoft/ai-agents-for-beginners | Skill | 79k | today | MIT | A | 200 | Claude Code, Codex |
| playwright-climicrosoft/playwright | Skill | 99k | today | Apache-2.0 | A | 19 | Claude Code |
| systematic-debuggingobra/superpowers | Skill | 314k | 3d ago | MIT | A | 21 | Claude Code |
| next-cache-components-adoptionvercel/next.js | Skill | 143k | today | MIT | A | 95 | Claude Code |
| chat-pet-sprite-creationmicrosoft/vscode | Skill | 195k | today | MIT | A | 53 | Claude Code, Codex |