resolve_todo_parallel

A command for resolving every unresolved TODO note found in a project's /todos directory. TODOs are reminders in code or documentation for work that still needs to be done.

In plain words
What is it for?
Finding TODO files, grouping their work, mapping dependencies, and dispatching one resolver for each eligible item.
Why use it?
It organizes related tasks, accounts for dependencies, and assigns separate work to handle items in parallel where possible.

Command

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.

agentmods
npx agentmods add commands/aegntic/compound-engineering/resolve_todo_parallel
Clone the repo
git clone --depth 1 https://github.com/aegntic/compound-engineering
Per session 13 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 479 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00013 $0.00479
Opus 5 $0.00006 $0.00239
Sonnet 5 $0.00003 $0.00096
Haiku 4.5 $0.00001 $0.00048

Measured 2d ago against content hash 4d5249bd4b42, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

resolve_todo_parallel 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 2d 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.

commands/resolve_todo_parallel.md · 40 lines

What it actually says

Resolve all TODO comments using parallel processing.

Workflow

1. Analyze

Get all unresolved TODOs from the /todos/*.md directory

If any todo recommends deleting, removing, or gitignoring files in docs/plans/ or docs/solutions/, skip it and mark it as wont_fix. These are compound-engineering pipeline artifacts that are intentional and permanent.

2. Plan

Create a TodoWrite list of all unresolved items grouped by type.Make sure to look at dependencies that might occur and prioritize the ones needed by others. For example, if you need to change a name, you must wait to do the others. Output a mermaid flow diagram showing how we can do this. Can we do everything in parallel? Do we need to do one first that leads to others in parallel? I'll put the to-dos in the mermaid diagram flow‑wise so the agent knows how to proceed in order.

3. Implement (PARALLEL)

Spawn a pr-comment-resolver agent for each unresolved item in parallel.

Before dispatching pr-comment-resolver, use the platform's file-search tool against the bundled agent directory to look for pr-comment-resolver.md, then use the file-read tool to load the full template. Only if the bundled template cannot be loaded should you fall back to ov_load_global_agent "pr-comment-resolver". Before dispatching, quote the first non-empty line of the loaded template and record the source used. If you cannot quote the template because it was not found or could not be read, stop execution, raise the missing-template issue, and do not dispatch. Never dispatch a named agent by name alone.

So if there are 3 comments, it will spawn 3 pr-comment-resolver agents in parallel. liek this

  1. Task pr-comment-resolver(comment1)
  2. Task pr-comment-resolver(comment2)
  3. Task pr-comment-resolver(comment3)

Always run all in parallel subagents/Tasks for each Todo item.

4. Commit & Resolve

  • Commit changes
  • Remove the TODO from the file, and mark it as resolved.
  • Push to remote
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. 2d ago First seen · 40 lines · 13 tokens per session scan A 4d5249bd4b42

Subscribe to this mod's changes

resolve_todo_parallel is a command published in the GitHub repository aegntic/compound-engineering (2 stars, last pushed 2mo ago), licensed MIT. It adds 13 tokens to every session and 479 once invoked, about $0.0001 per session on Opus 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-08-31.