agents-reverse-engineer: Command for Claude Code

.claude/commands/gsd/check-todos.md

gsd:check-todos is a command for Claude Code from GeoloeG-IsT/agents-reverse-engineer. It costs 16 tokens per session (1,556 once invoked), scanned A, original, MIT.

A command for reviewing pending todos captured during a work session. It shows the available tasks and lets the user choose one to inspect or continue.

In plain words
What is it for?
Listing todos, filtering them by area, viewing a selected todo's details and files, and checking whether it matches an upcoming roadmap phase.
Why use it?
It gives unfinished ideas and tasks a visible place, so they are less likely to be forgotten or left without a next step.

Command for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: names the AskUserQuestion tool.

This is GeoloeG-IsT/agents-reverse-engineer's own configuration. It tells Claude Code how to work on agents-reverse-engineer itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything agents-reverse-engineer configures →

Reuse

Borrowing it

Nothing to install: this file belongs to GeoloeG-IsT/agents-reverse-engineer. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/GeoloeG-IsT/agents-reverse-engineer/main/.claude/commands/gsd/check-todos.md
Clone the repo
git clone --depth 1 https://github.com/GeoloeG-IsT/agents-reverse-engineer

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 gsd:check-todos

README.md
[![agentmods](https://agentmods.dev/badge/commands/geoloeg-ist/agents-reverse-engineer/check-todos/github.svg)](https://agentmods.dev/commands/geoloeg-ist/agents-reverse-engineer/check-todos)
Your own site
<a href="https://agentmods.dev/commands/geoloeg-ist/agents-reverse-engineer/check-todos"><img src="https://agentmods.dev/badge/commands/geoloeg-ist/agents-reverse-engineer/check-todos/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 gsd:check-todos

Your own site · 80×15
<a href="https://agentmods.dev/commands/geoloeg-ist/agents-reverse-engineer/check-todos"><img src="https://agentmods.dev/badge/commands/geoloeg-ist/agents-reverse-engineer/check-todos.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 16 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,556 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.00016 $0.01556
Opus 5 $0.00008 $0.00778
Sonnet 5 $0.00003 $0.00311
Haiku 4.5 $0.00002 $0.00156

Measured 9d ago against content hash 5e450def8e2d, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

gsd:check-todos 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 9d 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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

.claude/commands/gsd/check-todos.md · 229 lines

How it starts

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

Enables reviewing captured ideas and deciding what to work on next.

If count is 0:

No pending todos.

Todos are captured during work sessions with /gsd:add-todo.

---

Would you like to:

1. Continue with current phase (/gsd:progress)
2. Add a todo now (/gsd:add-todo)

Exit.

Apply area filter if specified. Display as numbered list:

Pending Todos:

1. Add auth token refresh (api, 2d ago)
2. Fix modal z-index issue (ui, 1d ago)
3. Refactor database connection pool (database, 5h ago)

---

Reply with a number to view details, or:
- `/gsd:check-todos [area]` to filter by area
- `q` to exit

Format age as relative time.

If valid: load selected todo, proceed. If invalid: "Invalid selection. Reply with a number (1-[N]) or q to exit."

## [title]

**Area:** [area]
**Created:** [date] ([relative time] ago)
**Files:** [list or "None"]

### Problem
[problem section content]

### Solution
[solution section content]

If files field has entries, read and briefly summarize each.

If roadmap exists:

  1. Check if todo's area matches an upcoming phase
  2. Check if todo's files overlap with a phase's scope
  3. Note any match for action options

Use AskUserQuestion:

  • header: "Action"
  • question: "This todo relates to Phase [N]: [name]. What would you like to do?"
  • options:
    • "Work on it now" — move to done, start working
    • "Add to phase plan" — include when planning Phase [N]
    • "Brainstorm approach" — think through before deciding
    • "Put it back" — return to list

If no roadmap match:

Use AskUserQuestion:

  • header: "Action"
  • question: "What would you like to do with this todo?"
  • options:
    • "Work on it now" — move to done, start working
    • "Create a phase" — /gsd:add-phase with this scope
    • "Brainstorm approach" — think through before deciding
    • "Put it back" — return to list

Add to phase plan: Note todo reference in phase planning notes. Keep in pending. Return to list or exit.

Create a phase: Display: /gsd:add-phase [description from todo] Keep in pending. User runs command in fresh context.

Brainstorm approach: Keep in pending. Start discussion about problem and approaches.

Put it back: Return to list_todos step.

ls .planning/todos/pending/*.md 2>/dev/null | wc -l

Update STATE.md "### Pending Todos" section if exists.

Check planning config:

COMMIT_PLANNING_DOCS=$(cat .planning/config.json 2>/dev/null | grep -o '"commit_docs"[[:space:]]*:[[:space:]]*[^,}]*' | grep -o 'true\|false' || echo "true")
git check-ignore -q .planning 2>/dev/null && COMMIT_PLANNING_DOCS=false

Read the full file on GitHub · 229 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. 9d ago First seen · 229 lines · 16 tokens per session scan A 5e450def8e2d

Subscribe to this mod's changes

gsd:check-todos is a command published in the GitHub repository GeoloeG-IsT/agents-reverse-engineer (20 stars, last pushed 1mo ago), licensed MIT. It adds 16 tokens to every session and 1,556 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-30.