Borrowing it
Nothing to install: this file belongs to vishnu2kmohan/mcp-server-langgraph. 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/vishnu2kmohan/mcp-server-langgraph/main/.claude/commands/todo-status.mdgit clone --depth 1 https://github.com/vishnu2kmohan/mcp-server-langgraphWrote 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/vishnu2kmohan/mcp-server-langgraph/todo-status)<a href="https://agentmods.dev/commands/vishnu2kmohan/mcp-server-langgraph/todo-status"><img src="https://agentmods.dev/badge/commands/vishnu2kmohan/mcp-server-langgraph/todo-status.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.00012 | $0.02016 |
| Opus 5 | $0.00006 | $0.01008 |
| Sonnet 5 | $0.00002 | $0.00403 |
| Haiku 4.5 | $0.00001 | $0.00202 |
Grade A, and why
todo-status 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 6d 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 — 313 lines — stays where its author put it; the contents beside it link to each section on GitHub.
TODO Status Report (Enhanced)
Usage: /todo-status or /todo-status --burndown
Purpose: Generate comprehensive TODO status with git tracking and burndown analytics
Enhanced Features 🆕:
- ✅ Git-based historical tracking
- ✅ Burndown chart visualization
- ✅ Velocity calculation
- ✅ Trend analysis over time
- ✅ Predicted completion date
📊 TODO Status Generation (Enhanced)
Step 1: Run Enhanced TODO Tracker
Execute the automated TODO tracker with git integration:
# Standard scan
python scripts/workflow/todo-tracker.py --output /tmp/todo_scan.md
# With historical tracking (recommended)
python scripts/workflow/todo-tracker.py --output /tmp/todo_scan.md --track-history
Captures:
- All TODO comments in src/
- Grouped by priority (CRITICAL/HIGH/MEDIUM/LOW)
- Categorized by type (monitoring, compliance, testing, etc.)
- File locations with line numbers
- Git history of TODO changes 🆕
- Historical counts by commit 🆕
Step 2: Read TODO Catalog
Read the current TODO catalog:
cat docs-internal/TODO_CATALOG.md
Analyzes:
- Total items cataloged
- Items by priority
- Items by category
- Implementation status
- Deferred items
Step 3: Git History Analysis 🆕
Analyze TODO evolution using git:
# Count TODOs in recent commits (last 30 days)
git log --since="30.days.ago" --all --format="%H|%ad|%s" --date=short | while IFS='|' read hash date msg; do
count=$(git show $hash:src/ 2>/dev/null | grep -r "TODO" | wc -l)
echo "$date|$count|$msg"
done > /tmp/todo_history.txt
# Calculate velocity (TODOs resolved per day)
# Parse history and compute trend
Metrics Calculated:
- TODOs resolved per day (velocity)
- Average resolution rate (last 7/14/30 days)
- Trend direction (improving/stable/worsening)
- Projected completion date
Step 4: Enhanced Burndown Analysis 🆕
Generate visual ASCII burndown chart and comparison:
# Generate burndown visualization
python scripts/workflow/generate-burndown.py --days 30 --output /tmp/burndown.txt
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.
- 6d ago First seen · 313 lines · 12 tokens per session scan A d0a672f7d1df
todo-status is a command published in the GitHub repository vishnu2kmohan/mcp-server-langgraph (4 stars, last pushed 6d ago), licensed MIT. It adds 12 tokens to every session and 2,016 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.
Other commands, from other repositories
project-board-sync
Synchronize AI swarms with GitHub Projects for visual task management, progress tracking, and team coordination.
repo-architect
Repository structure optimization and multi-repo management with ruv-swarm coordination for scalable project architecture and development workflows.
swarm-issue
Transform GitHub Issues into intelligent swarm tasks, enabling automatic task decomposition and agent coordination.
sync-coordinator
Multi-package synchronization and version alignment with ruv-swarm coordination for seamless integration between claude-code-flow and ruv-swarm packages.
issue-tracker
Intelligent issue management and project coordination with ruv-swarm integration for automated tracking, progress monitoring, and team coordination.
orchestrator
Multi-agent task orchestration with TodoWrite/TodoRead/Task/Memory using MCP tools.