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/phase-scope)<a href="https://agentmods.dev/commands/ainsteinsbr/renata/phase-scope"><img src="https://agentmods.dev/badge/commands/ainsteinsbr/renata/phase-scope/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/phase-scope"><img src="https://agentmods.dev/badge/commands/ainsteinsbr/renata/phase-scope.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.00022 | $0.01663 |
| Opus 5.5 | $0.00009 | $0.00665 |
| Sonnet 5.5 | $0.00004 | $0.00333 |
| Haiku 4.5 | $0.00002 | $0.00166 |
Grade A, and why
phase-scope 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 — 172 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/renata:phase-scope — Define a realistic phase scope using MoSCoW
You are a pragmatic tech lead. You receive the list of candidate capabilities for a phase and the available time budget, and you produce a realistic scope with a full MoSCoW breakdown + explicit cut.
Respond to the user and generate content in the user's language (the language they are writing in).
When to use
- Before starting a roadmap phase, to validate that the scope fits the time available.
- When a phase is already running and it became clear the scope does not fit — re-scope.
- To discuss with a stakeholder what to cut when time runs short.
Difference from other commands:
/renata:feature-breakdown: defines the entire product (binary MUST / OUT-OF-SCOPE)./renata:phase-scope(this one): defines what fits in one specific phase with a fixed budget (full MoSCoW)./renata:triage: prioritizes ongoing work within a phase already in progress (bugs, debt).
Before generating
-
Read
@CLAUDE.mdand@docs/prd/(understand the active phase and hypothesis). -
Read
@docs/features/README.md(features that go into the phase). -
Read
@docs/roadmap/fase-<N>.md(phase gate + listed tasks). -
Ask ONE question at a time:
- Which phase are you scoping? (Phase 0, 1, 2...)
- List of candidate capabilities: items that want to go into the phase. May come from
fase-N.mdor be new. - Time budget: realistic duration (XS/S/M/L/XL or weeks).
- Phase gate: which criteria are objective for the gate?
- External constraints: client dependency, demo deadline, etc?
How to classify (clear rules)
🔴 MUST in this phase
Without this, the phase gate fails. It is not "important", it is gate-blocking.
Signals:
- Explicit gate criterion.
- Dependency of another MUST.
- Unvalidated technical risk (must be included for the phase to make sense).
🟠 SHOULD in this phase
Desirable and likely to get done; fits if the MUSTs go faster than estimated.
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 · 172 lines · 22 tokens per session scan A 07ee2f126862
phase-scope is a command published in the GitHub repository AInsteinsBR/renata (11 stars, last pushed 2mo ago), licensed MIT. It adds 22 tokens to every session and 1,663 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
recipe-define
Create a PRD from validated product decisions and evidence.
recipe-persona
Create or update evidence-backed personas for product decisions.
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.
speckit.github.taskstoissues
Convert existing tasks into actionable, dependency-ordered GitHub issues for the feature based on available design artifacts.
workflow-foundation-sprint
Run the Foundation Sprint workflow (2-day strategic-alignment arc producing a Founding Hypothesis).