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.reorg_headersgit 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.reorg_headers)<a href="https://agentmods.dev/skills/gpsaggese/helpers/todo.reorg_headers"><img src="https://agentmods.dev/badge/skills/gpsaggese/helpers/todo.reorg_headers/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.reorg_headers"><img src="https://agentmods.dev/badge/skills/gpsaggese/helpers/todo.reorg_headers.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.00034 | $0.01044 |
| Opus 5.5 | $0.00014 | $0.00418 |
| Sonnet 5.5 | $0.00007 | $0.00209 |
| Haiku 4.5 | $0.00003 | $0.00104 |
Grade A, and why
todo.reorg_headers 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- todo.reorg_headers — 89% identical, 35 lines differ
How it starts
The opening of the file, as written. The whole thing — 90 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Goal
- Align the H2 topic headers in
ai_task_queue.mdwith the canonical list inai_task_queue.md's# ALL TOPICSsection - Fold in stray H2 topics: add them to
# ALL TOPICSin the right place, or merge them into an existing topic - Move each H3 task under the correct H2 topic, without moving it out of its H1 stage
- Normalize every H3 task header to carry a checkbox marker, without changing markers that already exist
References
.claude/skills/todo.rules.md: defines the H1 stage / H2 topic / H3 task organization and the# ALL TOPICSmaster list
Workflow
Load the Conventions
- Read
.claude/skills/todo.rules.md - Read
ai_task_queue.md's# ALL TOPICSsection; record the ordered list of## <Topic>headers. The// <group>comments mark group boundaries, not topics
Reconcile the Topic Taxonomy
- For every other H1 stage in
ai_task_queue.md(IN PROGRESS,HIGH PRIORITY,BACKLOG,ICEBOX, ...) list its H2 headers - For each H2 header, check whether it matches (case-insensitively) an ALL TOPICS
entry
- Match -> keep it, using the exact ALL TOPICS spelling as the canonical header
- No match -> decide:
- If it clearly restates or overlaps an existing ALL TOPICS entry (e.g. "Build & Infrastructure" vs "Build is green"), merge: rename its header to the existing entry and fold its tasks under that topic
- If it is a genuinely new topic, add it to
# ALL TOPICSunder the closest matching// <group>comment (or a new group if none fits), then keep it as its own H2 - Placeholder headers with no descriptive name (e.g.
## ?) are never kept: classify every task under them individually by content instead of by header
- Do not guess on an ambiguous case: list it and ask the user to pick the merge target or a new topic before proceeding
- Apply merges and additions to
# ALL TOPICSfirst, so the rest of the pass has one final taxonomy to file tasks against
File Every H3 Task Under the Correct Topic
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 · 90 lines · 34 tokens per session scan A ea05dce80f21
todo.reorg_headers is a skill published in the GitHub repository gpsaggese/helpers (158 stars, last pushed today), licensed Apache-2.0. It adds 34 tokens to every session and 1,044 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.reorg_headers compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| todo.reorg_headersgpsaggese/helpers | Skill | 158 | today | Apache-2.0 | A | 34 | 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 |