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/SarutobiSasuke8/agentops-templateWrote 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/sarutobisasuke8/agentops-template/todo-triage)<a href="https://agentmods.dev/commands/sarutobisasuke8/agentops-template/todo-triage"><img src="https://agentmods.dev/badge/commands/sarutobisasuke8/agentops-template/todo-triage/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/sarutobisasuke8/agentops-template/todo-triage"><img src="https://agentmods.dev/badge/commands/sarutobisasuke8/agentops-template/todo-triage.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.00239 |
| Opus 5.5 | $0.00005 | $0.00096 |
| Sonnet 5.5 | $0.00003 | $0.00048 |
| Haiku 4.5 | $0.00001 | $0.00024 |
Grade A, and why
todo-triage 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.
What it actually says
Read TODO.md. If it does not exist, say so and stop.
Triage every item into one of three buckets:
Now — blocks current work, has a clear owner, or is fast and high-value. Soon — valuable but not urgent; needs a little more context or a decision first. Parking lot — speculative, stale, or dependent on something far out.
For each Now item, add:
- A one-line success criterion (what does "done" look like?)
- A suggested first action (command to run, file to read, question to answer)
Output format:
## Now
- [ ] <item> — <success criterion> | first action: <action>
## Soon
- [ ] <item>
## Parking lot
- [ ] <item>
Do not rewrite TODO.md unless the user asks. Surface the triage only.
If TODO.md is empty or has fewer than three items, say so and suggest what recurring categories belong there based on AGENTS.md and docs/PROJECT_BRIEF.md.
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 · 33 lines · 13 tokens per session scan A eb5ec64fa282
todo-triage is a command published in the GitHub repository SarutobiSasuke8/agentops-template (9 stars, last pushed 28d ago), licensed MIT. It adds 13 tokens to every session and 239 once invoked, about $0.0001 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-08-31.
Other commands, from other repositories
status
Display project status, active tracks, and next actions.
portfolio
Show a read-only hub-wide portfolio of canonical Ideas and active Projects without duplicating topic-owned records.
repo-architect
Repository structure optimization and multi-repo management with ruv-swarm coordination for scalable project architecture and development workflows.
test-management
Organize, classify, and trace Katalon True Platform/TestOps test assets. Use when you need to structure test cases into folders and suites, move or reorganize cases, search and find existing assets at scale, link or unlink requirements to test cases, or produce a requirement-to-test traceability report (which…
_closing
A set of closing rules for project-management commands that change the .pm/ project-management folder. It controls the language of summaries and links shown in the final response.
feature
Create a new feature via SDLC-based multi-agent collaboration.