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.
npx agentmods add commands/ainsteinsbr/renata/todogit clone --depth 1 https://github.com/AInsteinsBR/renataWrote 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/ainsteinsbr/renata/todo)<a href="https://agentmods.dev/commands/ainsteinsbr/renata/todo"><img src="https://agentmods.dev/badge/commands/ainsteinsbr/renata/todo.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 | $0.00029 | $0.01737 |
| Opus 5 | $0.00015 | $0.00869 |
| Sonnet 5 | $0.00006 | $0.00347 |
| Haiku 4.5 | $0.00003 | $0.00174 |
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 4d 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 — 111 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/renata:todo — Backlog of pending items (inline in the doc + central sync)
You manage the project's TODO backlog: pending items that do not block the current work but need to be recorded. The backlog lives in docs/backlog/todos.md, ordered by impact on progress.
Respond to the user and generate content in the user's language (the language they are writing in).
The flow has two sides that reconcile:
- Inline: the TODO is born glued to its context, on the originating line inside a doc.
- Central:
docs/backlog/todos.mdaggregates everything into a single, prioritizable view.
Step 0 — Resolve integration (before saving)
The capability for this operation is tasks. Before any write:
- Read
integrations:in.claude/rules.yaml. Does thetaskscapability have an entry? - No entry → operate 100% locally in
docs/backlog/todos.md(default behavior). Skip to the normal flow. - Has an entry, but the tools of the declared MCP are NOT available in the session → warn ("MCP
<name>declared fortasksbut unavailable — saving locally only") and operate locally. - Has an entry and the tools are available:
a. Save FIRST locally (
docs/backlog/todos.md+ inline marker). Local is the truth. b. Ifmirror: true→ ASK: "Mirror this TODO in<MCP>(create/update a card)?". If confirmed → push via MCP, note the external id (e.g.JIRA-123) next to the local item. If declined → it stays local only; mirror later. c. Ifmirror: false→ do not push a write.
Degradation pattern identical to
etapa-gate.sh(tool absent → warn, never block). Without an MCP,/renata:todoworks entirely locally.
When to use
- You used a provisional number/value in a doc (PRD, persona, metrics) and want to remember to validate it later — without blocking progress.
- You accumulated small scattered pending items and want a central view.
- You want to pull the next relevant pending item to work on.
- You closed a pending item and want to mark it done.
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.
- 4d ago First seen · 111 lines · 29 tokens per session scan A a14cefb29e42
todo is a command published in the GitHub repository AInsteinsBR/renata (10 stars, last pushed 13d ago), licensed MIT. It adds 29 tokens to every session and 1,737 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
issue-start
Load a DSSE issue spec and begin structured work.
issue-approve
Approve the planned DSSE issue and transition it from open to in-progress.
issue-amend
Re-snapshot the active issue's scope from the spec, clear verified and reviewed receipts, and record the change as a permanent amendment.
prd-split
Split the approved PRD into one issue spec per manifest entry.
plan-okrs
Brainstorm team-level OKRs aligned with company objectives — qualitative objectives with measurable key results.
write-stories
Break a feature into backlog items — user stories, job stories, or WWA format with acceptance criteria.