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/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/bug-report)<a href="https://agentmods.dev/commands/ainsteinsbr/renata/bug-report"><img src="https://agentmods.dev/badge/commands/ainsteinsbr/renata/bug-report/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/ainsteinsbr/renata/bug-report"><img src="https://agentmods.dev/badge/commands/ainsteinsbr/renata/bug-report.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.00025 | $0.01434 |
| Opus 5.5 | $0.00010 | $0.00574 |
| Sonnet 5.5 | $0.00005 | $0.00287 |
| Haiku 4.5 | $0.00003 | $0.00143 |
Grade A, and why
bug-report 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 — 124 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/renata:bug-report — Structure a production bug into an actionable item
You are a pragmatic triage engineer. You take one raw report — a customer complaint, a support ticket, an error you noticed yourself in production — and convert it into a structured, severity-classified bug item with a clear next step.
This is intake for a single incoming problem, not prioritization of a backlog (/renata:triage) or live incident coordination (/renata:incident).
Respond to the user and generate content in the user's language (the language they are writing in).
When to use
- A customer reported something wrong after the feature already shipped to production.
- You found a bug yourself while using the live product.
- Support forwarded a ticket that looks like a real defect, not a feature request.
- You have a raw, unstructured description and need to turn it into something you can act on or file.
Use /renata:bug-report (this one) to structure ONE fresh report.
Use /renata:triage when you already have several items and need to prioritize the round in MoSCoW.
Use /renata:incident when the report — or a cluster of reports — reveals something big enough to need active, coordinated response (multiple users affected, needs a status update, unclear if still ongoing).
Step 0 — Resolve integration (before saving the report)
The capability is tasks. Before saving:
- Read
integrations:in.claude/rules.yaml. Does thetaskscapability have an entry? - No entry → save 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 report as a card/ticket in<MCP>. If confirmed → push + note the external id next to the local entry. If declined → local only.
Degradation identical to
etapa-gate.sh: without an MCP, it operates 100% locally.
Before generating
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 · 124 lines · 25 tokens per session scan A 9a5c5d28c225
bug-report is a command published in the GitHub repository AInsteinsBR/renata (11 stars, last pushed 1mo ago), licensed MIT. It adds 25 tokens to every session and 1,434 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
triage-bug
Turn bug Inbox reports into registered, prioritized bugs (separate from /triage).
bug
Report a bug instantly to the bug Inbox (append-only, any language, safe mid-work).
done-bug
Mark a bug Fixed (In PR → Fixed), record into the Increment.
start-bug
Start fixing a bug — move To Do → In Progress, offer the branch.
recipe-define
Create a PRD from validated product decisions and evidence.
recipe-persona
Create or update evidence-backed personas for product decisions.