Borrowing it
Nothing to install: this file belongs to zhangreling02-ai/3dslicer-claude-bridge. 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/zhangreling02-ai/3dslicer-claude-bridge/main/.claude/commands/todo.mdgit clone --depth 1 https://github.com/zhangreling02-ai/3dslicer-claude-bridgeWrote 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/zhangreling02-ai/3dslicer-claude-bridge/todo)<a href="https://agentmods.dev/commands/zhangreling02-ai/3dslicer-claude-bridge/todo"><img src="https://agentmods.dev/badge/commands/zhangreling02-ai/3dslicer-claude-bridge/todo/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/commands/zhangreling02-ai/3dslicer-claude-bridge/todo"><img src="https://agentmods.dev/badge/commands/zhangreling02-ai/3dslicer-claude-bridge/todo.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.00000 | $0.00461 |
| Opus 5 | $0.00000 | $0.00230 |
| Sonnet 5 | $0.00000 | $0.00092 |
| Haiku 4.5 | $0.00000 | $0.00046 |
Grade A, and why
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 11d 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.
What it actually says
/todo - PR Review TODO List
Display and manage the PR #22 review items.
Description
This command reads the TODO.md file and provides a summary of pending items from the PR review analysis (silent-failure-hunter and pr-test-analyzer agents).
Usage
/todo # Show summary and next recommended action
/todo status # Count pending vs completed items
/todo next # Show the next highest-priority item to work on
Instructions
When the user invokes this command:
- Read TODO.md from the project root
- Count items by parsing checkbox state:
- [ ]= pending- [x]= completed
- Categorize by priority:
- Critical (search for "Critical")
- High Priority (search for "High")
- Medium Priority (search for "Medium")
- Low Priority (search for "Low")
- Display summary in this format:
📋 PR #22 Review Items
Status: X/Y completed
🔴 Critical: N pending
🟠 High: N pending
🟡 Medium: N pending
🟢 Low: N pending
Next recommended action:
→ [First unchecked Critical item, or first High if no Critical]
Quick commands:
- Edit TODO.md to mark items complete
- Run: uv run pytest -v to verify fixes
-
If
$ARGUMENTSis "next": Show only the next item to work on with its full context (file path, line numbers, fix instructions) -
If
$ARGUMENTSis "status": Show just the counts without recommendations
Context
This TODO list was generated from PR review agents analyzing the refactor/code-quality-improvements branch. Items include:
- Silent failure patterns that mask errors
- Missing test coverage for new code
- Error handling improvements
Related Files
TODO.md- The actual todo list.claude/plans/deep-plotting-gem.md- Full implementation planref/resilience-patterns.md- Documentation on error handling 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.
- 11d ago First seen · 66 lines · 0 tokens per session scan A 9d156a00786c
todo is a command published in the GitHub repository zhangreling02-ai/3dslicer-claude-bridge (0 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 461 tokens. 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.
Other commands, from other repositories
sdd-init
Initialize SDD context — detects project stack and bootstraps persistence backend.
review-branch
Review the current branch's diff against base by dispatching atomic-reviewer. No orchestration loop, no spec required — pre-flight before /commit pr or /commit merge.
init
Install the formatters this repository needs, with every command visible before it runs.
repo-audit
Audit a codebase (local or remote GitHub/GitLab) against architecture principles and requirements, surfacing drift, risk, and missing decisions.
argos
A command for checking whether an implementation matches its design deliverables. Its Korean description compares the work to the design as part of a completion inspection.
security-review
AI-powered security review of the current git diff (or specified paths). Dispatches the security-reviewer agent and prints findings grouped by severity.