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/executegit clone --depth 1 https://github.com/AInsteinsBR/renataWhat 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.00022 | $0.01630 |
| Opus 5 | $0.00011 | $0.00815 |
| Sonnet 5 | $0.00004 | $0.00326 |
| Haiku 4.5 | $0.00002 | $0.00163 |
Grade A, and why
execute 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 2d 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 — 89 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/renata:execute — Orchestrate Step 12 (execute the plan) while respecting the method
You are a tech lead leading the execution of a phase. This command is the output mirror of /renata:plan-phase: just as /renata:plan-phase won't let you start without the 11 prerequisites, /renata:execute won't let you close a task without verification.
Respond to the user in the user's language (the language they are writing in).
It orchestrates superpowers:executing-plans with the RENATA guardrails, wiring the skills/agents at the right moment of each task. On its own, executing-plans does not know our method or our done gate.
When to use
- To execute a roadmap phase that already has a plan approved by
@architect(output of Step 11 //renata:plan-phase).
Do NOT use for:
- Generating the plan →
/renata:plan-phase. - Technical investigation →
/renata:spike. - Structural decision →
/renata:adr.
Step 1 — Pre-flight (prerequisite validation)
Validate the 5 items below, listing the result of each. If any fails, abort and instruct the fix.
| # | Prerequisite | How to validate | Failure → |
|---|---|---|---|
| 0 | The superpowers plugin is installed (external dependency) |
The superpowers:executing-plans skill is available in this session |
Abort — do NOT improvise the execution loop by hand. "Install the superpowers plugin first (/plugin marketplace add obra/superpowers + /plugin install superpowers@superpowers-dev), then re-run /renata:execute." |
| 1 | An approved plan exists in docs/superpowers/plans/ |
ls docs/superpowers/plans/*-plan.md returns ≥1 and CLAUDE.md Section 5 points to it |
"Run /renata:plan-phase <phase> first." |
| 2 | Plan with no open 🔴 blockers from @architect |
grep -c "🔴" docs/superpowers/plans/<plan> — confirm the 🔴 are marked as resolved |
"Resolve the @architect blockers first." |
| 3 | No other overlapping running plan for the same phase |
only 1 plan for the phase with Status: running |
"Finish or abandon the previous plan first." |
| 4 | rules.yaml valid |
bash "${CLAUDE_PLUGIN_ROOT}/hooks/scripts/rules-violation.sh" runs without a fatal error |
"Run /renata:adr in refine mode to populate rules.yaml." |
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.
- 2d ago First seen · 89 lines · 22 tokens per session scan A 5f4ac5b77969
execute is a command published in the GitHub repository AInsteinsBR/renata (10 stars, last pushed 11d ago), licensed MIT. It adds 22 tokens to every session and 1,630 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-closeout
Triage Codex findings via per-finding dispositions, mark findingstriaged, close the active issue.
issue-review
Run Codex native + adversarial review against the active issue, scoped to allowedfiles, capped per kind.
prd-review
Review the active PRD with Codex and stream normalized findings to JSONL.
prd-triage
Triage pending findings on the active PRD.
prd-archive
Archive the active PRD (terminal state).
issue-start
Load a DSSE issue spec and begin structured work.