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.
curl -O https://raw.githubusercontent.com/GeoloeG-IsT/agents-reverse-engineer/main/.claude/commands/gsd/add-todo.mdgit clone --depth 1 https://github.com/GeoloeG-IsT/agents-reverse-engineerWrote 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/commands/geoloeg-ist/agents-reverse-engineer/add-todo)<a href="https://agentmods.dev/commands/geoloeg-ist/agents-reverse-engineer/add-todo"><img src="https://agentmods.dev/badge/commands/geoloeg-ist/agents-reverse-engineer/add-todo.svg" alt="Measured on agentmods" 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.00016 | $0.01304 |
| Opus 5 | $0.00008 | $0.00652 |
| Sonnet 5 | $0.00003 | $0.00261 |
| Haiku 4.5 | $0.00002 | $0.00130 |
Grade A, and why
gsd:add-todo 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 7d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- gsd:add-todo — 98% identical, 2 lines differ
How it starts
The opening of the file, as written. The whole thing — 194 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Enables "thought → capture → continue" flow without losing context or derailing current work.
Note existing areas for consistency in infer_area step.
Without arguments: Analyze recent conversation to extract:
- The specific problem, idea, or task discussed
- Relevant file paths mentioned
- Technical details (error messages, line numbers, constraints)
Formulate:
title: 3-10 word descriptive title (action verb preferred)problem: What's wrong or why this is neededsolution: Approach hints or "TBD" if just an ideafiles: Relevant paths with line numbers from conversation
| Path pattern | Area |
|---|---|
src/api/*, api/* |
api |
src/components/*, src/ui/* |
ui |
src/auth/*, auth/* |
auth |
src/db/*, database/* |
database |
tests/*, __tests__/* |
testing |
docs/* |
docs |
.planning/* |
planning |
scripts/*, bin/* |
tooling |
| No files or unclear | general |
Use existing area from step 2 if similar match exists.
If potential duplicate found:
- Read the existing todo
- Compare scope
If overlapping, use AskUserQuestion:
- header: "Duplicate?"
- question: "Similar todo exists: [title]. What would you like to do?"
- options:
- "Skip" — keep existing todo
- "Replace" — update existing with new context
- "Add anyway" — create as separate todo
Generate slug from title (lowercase, hyphens, no special chars).
Write to .planning/todos/pending/${date_prefix}-${slug}.md:
---
created: [timestamp]
title: [title]
area: [area]
files:
- [file:lines]
---
## Problem
[problem description - enough context for future Claude to understand weeks later]
## Solution
[approach hints or "TBD"]
- Count todos:
ls .planning/todos/pending/*.md 2>/dev/null | wc -l - Update "### Pending Todos" under "## Accumulated Context"
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
If COMMIT_PLANNING_DOCS=false: Skip git operations, log "Todo saved (not committed - commit_docs: false)"
If COMMIT_PLANNING_DOCS=true (default):
git add .planning/todos/pending/[filename]
[ -f .planning/STATE.md ] && git add .planning/STATE.md
git commit -m "$(cat <<'EOF'
docs: capture todo - [title]
Area: [area]
EOF
)"
Confirm: "Committed: docs: capture todo - [title]"
[title] Area: [area] Files: [count] referenced
Would you like to:
- Continue with current work
- Add another todo
- View all todos (/gsd:check-todos)
</step>
</process>
<output>
- `.planning/todos/pending/[date]-[slug].md`
- Updated `.planning/STATE.md` (if exists)
</output>
<anti_patterns>
- Don't create todos for work in current plan (that's deviation rule territory)
- Don't create elaborate solution sections — captures ideas, not plans
- Don't block on missing information — "TBD" is fine
</anti_patterns>
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.
- 7d ago First seen · 194 lines · 16 tokens per session scan A 4463e886dc56
gsd:add-todo 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,304 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.
Other commands, from other repositories
todo.template
This prompt was authored for Claude-style slash workflows. In Codex runtime, adapt tool calls as follows.
pulse-check
Pulse and worker utilisation diagnostics across repos.json, with self-improvement recommendations.
optimise-linux-indexing-backups
Audit and optionally apply safe Linux indexing and backup exclusions.
optimise-macos-indexing-backups
Audit and optionally apply safe macOS indexing and backup exclusions.
build-agent
Scaffold a new AI DevOps agent — service, tool, or workflow subagent with YAML frontmatter, placement decision, and cross-reference discovery.
email-delivery-test
../../services/email/email-delivery-test.md.