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/terrene-foundation/kailash-coc-claude-pyWrote 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/terrene-foundation/kailash-coc-claude-py/todos)<a href="https://agentmods.dev/commands/terrene-foundation/kailash-coc-claude-py/todos"><img src="https://agentmods.dev/badge/commands/terrene-foundation/kailash-coc-claude-py/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/terrene-foundation/kailash-coc-claude-py/todos"><img src="https://agentmods.dev/badge/commands/terrene-foundation/kailash-coc-claude-py/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.00013 | $0.01981 |
| Opus 5 | $0.00006 | $0.00991 |
| Sonnet 5 | $0.00003 | $0.00396 |
| Haiku 4.5 | $0.00001 | $0.00198 |
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 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.
How it starts
The opening of the file, as written. The whole thing — 112 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Workspace Resolution
- If
$ARGUMENTSspecifies a project name, useworkspaces/$ARGUMENTS/ - Otherwise, use the most recently modified directory under
workspaces/(excludinginstructions/) - If no workspace exists, ask the user to create one first
- Read all files in
workspaces/<project>/briefs/for user context (this is the user's input surface)
Phase Check
- Read files in
workspaces/<project>/02-plans/for context - Read
specs/_index.mdand all relevant spec files for domain truth (MUST — seerules/specs-authority.md). Ifspecs/_index.mddoes not exist, STOP — return to/analyzeStep 5. Do NOT create specs during /todos. - Read ALL journal entries from
/analyzephase — especially DECISION, TRADE-OFF, and DISCOVERY types. Journal is a read-gate, not just a write-gate. - Check if
todos/active/already has files (resuming) - All todos go into
workspaces/<project>/todos/active/
Execution Model
This phase executes under the autonomous execution model (see rules/autonomous-execution.md). All effort estimates in todos MUST use autonomous execution cycles, not human-days. When referencing external plans that estimate in human-days, apply the 10x multiplier to translate. Do not phase work based on "team bandwidth" — phase based on dependency order and validation gates.
Per-session capacity budget (MUST): Each todo MUST fit within a single session's capacity — ≤500 LOC load-bearing logic, ≤5–10 simultaneous invariants, ≤3–4 call-graph hops, describable in 3 sentences. See rules/autonomous-execution.md § Per-Session Capacity Budget. Todos that exceed the budget MUST be sharded at this phase, not deferred to /implement.
The /todos approval gate is a structural gate: the human approves the plan (what and why), not the execution (how and when). Once approved, /implement executes autonomously.
Workflow
1. Review plans with specialists
Reference plans in workspaces/<project>/02-plans/ and work through every single file.
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.
- 9d ago First seen · 112 lines · 13 tokens per session scan A f1f4c0c6b802
todos is a command published in the GitHub repository terrene-foundation/kailash-coc-claude-py (12 stars, last pushed 24d ago), licensed Apache-2.0. It adds 13 tokens to every session and 1,981 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-09-03.
Other commands, from other repositories
template
Manage issue templates for streamlined issue creation.
sync-linear
Sync current work with Linear ticket status.
add-note
Add an internal or external note to a ConnectWise PSA ticket.
fest-show
Show festival progression (in-progress tasks, roadmap, and dependency view).
dispatcher
Pick the next-best repo to work on across the portfolio — rank free repos, recommend one, claim its lease atomically, and route to the entry command.
workpm
A project-management workflow for coordinating multiple AI workers through five stages. It includes task assignment, shared activity logs, worker replacement, and final checks.