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/user-journey)<a href="https://agentmods.dev/commands/ainsteinsbr/renata/user-journey"><img src="https://agentmods.dev/badge/commands/ainsteinsbr/renata/user-journey.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.1 | $0.00031 | $0.01093 |
| Opus 5 | $0.00015 | $0.00547 |
| Sonnet 5 | $0.00006 | $0.00219 |
| Haiku 4.5 | $0.00003 | $0.00109 |
Grade A, and why
user-journey 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 7d 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 — 110 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/renata:user-journey — Maps a persona's journey
You are a product researcher. You receive the name of a persona in $ARGUMENTS and map the before / during / after journey, appending it to docs/business-context/jornada.md.
Respond to the user and generate content in the user's language (the language they are writing in).
Before generating
- Read
@docs/business-context/personas.md— the persona must exist. - Read
@CLAUDE.mdto understand the product. - If
docs/discovery/*.mdexists, read the "How they solve it today" seed as a starting point for the before of the journey — but still map the full before/during/after with the dedicated rigor. The seed is a starting point, not a substitute. - If the persona does not exist, instruct the user to run
/renata:persona {{name}}first and abort.
Journey structure
3 phases, each with 4-7 steps:
- BEFORE — how the persona solves it today (without the product). Focus on pains and workarounds.
- DURING — how they solve it with the product. Focus on the idealized flow.
- AFTER — what changes in their life. Focus on ROI and metrics.
⚠️ Constraints of the journey syntax (important!)
mermaid journey is finicky with syntax. Silent constraints that break the render:
- ❌ NEVER use
:in the step text —:is a separator (step: note: actor). Use-or nothing. - ❌ Notes are always a number 1-5, never text. Do not write "bad", write
1. - ✅ Parentheses only in
section(not in the step name).section Before (today, without the product)is OK.Searches (quickly) in the menubreaks. - ✅ Avoid heavy accents in some viewers. Mermaid Chart 11.x accepts them, but if the diagram goes to Notion/GitHub-old, prefer no accents.
- ✅ Each section has 1-7 steps. More than 7 = fragment into more sections.
Use a journey mermaid (all notes are numbers 1-5, never text):
journey
title {{Persona}} {{task context}}
section Before (today, without the product)
step 1: 2: persona
step 2: 1: persona
section During (with the product)
step 1: 4: persona
step 2: 5: persona
section After
step: 5: persona
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.
- 7d ago First seen · 110 lines · 31 tokens per session scan A 0d76d3421a57
user-journey is a command published in the GitHub repository AInsteinsBR/renata (10 stars, last pushed 17d ago), licensed MIT. It adds 31 tokens to every session and 1,093 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
recipe-blueprint
Define the structural design context needed by a prototype or PRD.
recipe-define
Create a PRD from validated product decisions and evidence.
recipe-discover
Frame product opportunities and create decision-relevant hypotheses.
recipe-persona
Create or update evidence-backed personas for product decisions.
recipe-prototype-prompt
Export an evidence-grounded prompt for an external prototype generator.
recipe-refine-visuals
Refine the auto-derived Visual Tokens with a design-capable human.