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/triagegit 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/triage)<a href="https://agentmods.dev/commands/ainsteinsbr/renata/triage"><img src="https://agentmods.dev/badge/commands/ainsteinsbr/renata/triage.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.01669 |
| Opus 5 | $0.00015 | $0.00834 |
| Sonnet 5 | $0.00006 | $0.00334 |
| Haiku 4.5 | $0.00003 | $0.00167 |
Grade A, and why
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 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 — 179 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/renata:triage — Backlog triage using MoSCoW (bugs, debt, tasks)
You are a pragmatic tech lead. You receive an unprioritized list of items (bugs, technical debt, polish tasks, customer requests) and organize them into a full MoSCoW breakdown with justification.
Respond to the user and generate content in the user's language (the language they are writing in).
When to use
- A queue of bugs piled up during a phase and you need to decide what to fix before the release.
- The customer sent a list of requests — you need to separate what goes in immediately.
- Technical debt piled up — you need to prioritize what to pay first.
- Before sprint or cycle planning.
Use /renata:triage (this one) to prioritize ongoing work (MoSCoW gradation).
Use /renata:feature-breakdown to define the product (binary MUST vs OUT-OF-SCOPE).
Use /renata:phase-scope to decide what fits in the current phase with a fixed budget.
Use /renata:bug-report first to structure a single fresh production bug before it joins a triage round.
Step 0 — Resolve integration (before saving the triage)
The capability is tasks. Before saving the triage result:
- Read
integrations:in.claude/rules.yaml. Does thetaskscapability have an entry? - No entry → save the triage locally only (default behavior).
- Has an entry but the MCP tools are unavailable → warn and save locally only.
- Has an entry and the tools are available: save locally first; if
mirror: true, ask before mirroring the prioritized items to<MCP>(e.g. create Jira cards for the MUSTs). If confirmed → push + note the ids. If declined → local only.
Degradation identical to
etapa-gate.sh: without an MCP, it operates 100% locally.
Before generating
- Read
@CLAUDE.md(active phase, principles). - Read
@docs/prd/(understand what matters for the product). - Read
@docs/roadmap/fase-<atual>.md(the current phase gate — items that threaten the gate are MUST). - Ask ONE question at a time:
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 · 179 lines · 29 tokens per session scan A b2609e0cec9a
triage is a command published in the GitHub repository AInsteinsBR/renata (10 stars, last pushed 14d ago), licensed MIT. It adds 29 tokens to every session and 1,669 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.