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.
git clone --depth 1 https://github.com/khanh-vu/claude-forceWrote 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/khanh-vu/claude-force/todos)<a href="https://agentmods.dev/commands/khanh-vu/claude-force/todos"><img src="https://agentmods.dev/badge/commands/khanh-vu/claude-force/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.
<a href="https://agentmods.dev/commands/khanh-vu/claude-force/todos"><img src="https://agentmods.dev/badge/commands/khanh-vu/claude-force/todos.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.00006 | $0.02255 |
| Opus 5.5 | $0.00002 | $0.00902 |
| Sonnet 5.5 | $0.00001 | $0.00451 |
| Haiku 4.5 | $0.00001 | $0.00226 |
Grade A, and why
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 1mo 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 — 406 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Todos Command
Quick capture for ideas, tasks, and reminders without leaving your workflow.
When to Use
Use /todos for:
- Quick ideas during work (mid-workflow capture)
- Reminders for later
- Exploratory notes
- Task backlog management
Use /new-task for:
- Formal task definition with structured requirements
- Agent orchestration and workflow execution
- Production work with validation
Pro tip: Use /todos to capture, then convert to /new-task when ready to execute.
Quick Add
Capture an idea instantly:
/todos --add "Fix performance issue in ProductList component"
What happens:
- Creates
.claude/TO-DOS.mdif it doesn't exist - Generates unique todo ID
- Prompts for additional context (or accepts minimal input)
- Suggests relevant agents/workflows automatically
- Checks for similar existing todos
Output:
✅ Added todo: todo-20251116-143022-a3f4b2
Similar todos found:
1. Optimize ProductList rendering (added 2 days ago)
Continue with new todo? (y/n): y
💡 Suggested agents: frontend-developer, performance-expert
💡 Suggested workflow: performance-optimization
Todo saved to .claude/TO-DOS.md
View All Todos
List and select todos interactively:
/todos
or
/todos --list
Output:
# Active Todos (5)
## 🔄 In Progress (1)
**1** 🔴 Refactor authentication module
**Why**: Improve security and maintainability
**Files**: src/auth/auth.ts:45-120
**Added**: 2 hours ago
**Suggested**: backend-architect, security-specialist
## 🔴 High Priority (2)
**2** Fix performance issue in ProductList component
**Why**: Page load takes 3+ seconds with 100 items
**Files**: src/components/ProductList.tsx:67-89
**Added**: 1 hour ago
**Suggested**: frontend-developer, performance-expert
**3** Add comprehensive error handling
**Why**: Users see generic errors, hard to debug
**Files**: src/api/client.ts
**Added**: 3 hours ago
**Suggested**: backend-architect
## 🟡 Medium Priority (2)
**4** Update API documentation
**Why**: Endpoints changed but docs outdated
**Added**: 1 day ago
**Suggested**: document-writer-expert
**5** Investigate caching strategy
**Why**: Explore Redis vs in-memory for session data
**Added**: 2 days ago
**Suggested**: backend-architect
---
Select todo (1-5), or:
[a] Add new todo
[c] Archive completed
[0] Cancel
Your choice:
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.
- 1mo ago First seen · 406 lines · 6 tokens per session scan A 5ed5be295153
todos is a command published in the GitHub repository khanh-vu/claude-force (6 stars, last pushed 11mo ago), licensed MIT. It adds 6 tokens to every session and 2,255 once invoked, about $0.0000 per session on Opus 5.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-09-03.
Other commands, from other repositories
standup
Quick daily standup from today's Claude Code sessions — grouped by project, with cost and errors.
show-your-work
Keep a reviewable TSV decision trail for long-running or unattended work. Usage: /show-your-work [task-slug].
scout-meta-review
Run an interactive Scout meta-review — a system-level audit that sits above the individual session types. Checks whether sessions are running, mistake audit is trending well, proposals are flowing, KB files are healthy, and data-source coverage is consistent across session types. Runs in the current conversation.
ops
Weekly operations loop — triage the inquiry inbox, advance the CRM pipeline, sweep open PRs across repos, and surface the content plan. Loads the ops skill.
fire-todos
Capture, list, and manage todos during work sessions.
todo.template
This prompt was authored for Claude-style slash workflows. In Codex runtime, adapt tool calls as follows.