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.reorg_in_progress/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.reorg_in_progress)<a href="https://agentmods.dev/skills/causify-ai/helpers/todo.reorg_in_progress"><img src="https://agentmods.dev/badge/skills/causify-ai/helpers/todo.reorg_in_progress/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.reorg_in_progress"><img src="https://agentmods.dev/badge/skills/causify-ai/helpers/todo.reorg_in_progress.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.00029 | $0.01420 |
| Opus 5.5 | $0.00012 | $0.00568 |
| Sonnet 5.5 | $0.00006 | $0.00284 |
| Haiku 4.5 | $0.00003 | $0.00142 |
Grade A, and why
todo.reorg_in_progress 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 29d 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 — 110 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Goal
- Move every
### [.] <Title>task (in progress) into the# IN PROGRESSsection, under its topic's(IN PROGRESS)H2 - Move every
### [ ] <Title>task (not started) that sits under# IN PROGRESSinto# BACKLOG, under its topic's(BACKLOG)H2 - Move any H2 topic header whose
(<Stage>)suffix doesn't match its enclosing H1 stage to the H1 stage the suffix names, together with all its tasks - Leave
### [x] ...tasks and nested checklist items (- [ ],- [x],- [.]) untouched
References
.claude/skills/todo.rules.md: defines the H1 stage / H2 topic / H3 task organization and the## <Topic> (<Stage>)header convention
Workflow
Load the Conventions
- Read
.claude/skills/todo.rules.md - Identify the H1 stage headers present in
ai_task_queue.md(e.g.# IN PROGRESS,# BACKLOG - HIGH PRIORITY,# BACKLOG,# ICEBOX,# ALL TOPICS) - Never touch the
# ALL TOPICSsection in this skill
Phase 1: Refile Mislabeled H2 Topics
- Do this phase first: fixing a misfiled topic before the task-marker rules run keeps the topic's tasks together instead of letting Phase 2/3 split them across stages
- For every H2 header
## <Topic> (<Stage>)found outside# ALL TOPICS:- Compare
<Stage>to the name of its enclosing H1 - Mismatch -> cut the entire H2 block (the header line through everything up to the
next H2 or H1) and move it under the H1 that matches
<Stage>- If an H2 with the same bare
<Topic>already exists under that H1, append the moved block's task content there and drop the duplicate header line, instead of creating a second header for the same topic - Otherwise, insert the moved H2 block at the end of that H1's section (right before the next H1 header)
- If
<Stage>names an H1 that does not exist anywhere in the file, do not create it silently: list the header and ask the user whether to create that stage or use a different one
- If an H2 with the same bare
- Keep the moved block's content (task titles, markers, bodies) byte-for-byte unchanged aside from its position
- Example:
## Noesis (BACKLOG - HIGH PRIORITY)sitting under# IN PROGRESSis cut and moved, with all its### ...tasks, under# BACKLOG - HIGH PRIORITY
- Compare
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.
- 29d ago First seen · 110 lines · 29 tokens per session scan A 332689805b02
todo.reorg_in_progress is a skill published in the GitHub repository causify-ai/helpers (150 stars, last pushed today), licensed Apache-2.0. It adds 29 tokens to every session and 1,420 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-18.
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…