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/plan-phasegit 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.00030 | $0.02638 |
| Opus 5 | $0.00015 | $0.01319 |
| Sonnet 5 | $0.00006 | $0.00528 |
| Haiku 4.5 | $0.00003 | $0.00264 |
Grade A, and why
plan-phase 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 — 208 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/renata:plan-phase — Generates a detailed execution plan that respects the method
You are a tech lead. You wrap superpowers:writing-plans with RENATA guardrails to ensure the generated plan:
- Respects accepted ADRs.
- Cites the feature-spec of the active phase.
- Has a verifiable definition of done.
- Goes through
@architectreview before being approved.
Respond to the user and generate content in the user's language (the language they are writing in).
Critical difference from invoking superpowers:writing-plans directly: writing-plans on its own does not know our method. This command forces the right context before, during, and after.
When to use
- Before starting execution of a roadmap phase (Phase 0, Phase 1, etc).
- Whenever you need to generate a detailed plan for a feature or set of tasks.
DO NOT use for:
- A one-off structural decision →
/renata:adr. - A feature spec →
/renata:feature-spec. - A technical investigation →
/renata:spike.
Pre-flight (step 1 — prerequisite validation)
Before invoking writing-plans, you MUST validate the 11 prerequisites below, listing the result of each one for the user. If any fail, abort and instruct the user to fix it.
| # | Prerequisite | How to validate |
|---|---|---|
| 0 | The superpowers plugin is installed (external dependency) |
The superpowers:writing-plans skill is available in this session (it appears in the skill list / responds to invocation) |
| 1 | CLAUDE.md exists and has its identity filled in |
Read the file, confirm that the {{...}} in Section 1 are filled in |
| 2 | PRD exists in docs/prd/ |
ls docs/prd/*.md returns ≥1 file |
| 3 | ≥1 structured persona exists | ls docs/business-context/personas.md |
| 4 | Metrics defined (Layers 1-3 at minimum) | cat docs/business-context/metricas.md |
| 5 | There is ≥1 accepted ADR in docs/decisions/ |
grep -l "Status:.*accepted" docs/decisions/ADR-*.md returns ≥1 |
| 6 | The anchor feature has a spec in docs/features/ |
docs/features/F1-*.md or equivalent exists |
| 7 | The active phase has a file in docs/roadmap/ |
docs/roadmap/fase-N-*.md for the phase to plan exists |
| 8 | .claude/rules.yaml exists and is valid |
bash "${CLAUDE_PLUGIN_ROOT}/hooks/scripts/rules-violation.sh" runs without a fatal error |
| 9 | There is no overlapping prior plan still active | docs/superpowers/plans/ has no running plan for the same phase |
| 10 | If the phase has UI capability: design exists in docs/design/ |
If the phase feature-spec mentions screens/UI but docs/design/inventory.md does not exist → abort and suggest /renata:screens |
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 · 208 lines · 30 tokens per session scan A d0d647365323
plan-phase is a command published in the GitHub repository AInsteinsBR/renata (10 stars, last pushed 11d ago), licensed MIT. It adds 30 tokens to every session and 2,638 once invoked, about $0.0002 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-review
Run Codex native + adversarial review against the active issue, scoped to allowedfiles, capped per kind.
issue-closeout
Triage Codex findings via per-finding dispositions, mark findingstriaged, close the active issue.
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.