Borrowing it
Nothing to install: this file belongs to DanielPodolsky/ownyourcode. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/DanielPodolsky/ownyourcode/main/.claude/commands/own/retro.mdgit clone --depth 1 https://github.com/DanielPodolsky/ownyourcodeWrote 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/danielpodolsky/ownyourcode/retro)<a href="https://agentmods.dev/commands/danielpodolsky/ownyourcode/retro"><img src="https://agentmods.dev/badge/commands/danielpodolsky/ownyourcode/retro/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/danielpodolsky/ownyourcode/retro"><img src="https://agentmods.dev/badge/commands/danielpodolsky/ownyourcode/retro.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.00014 | $0.02007 |
| Opus 5.5 | $0.00006 | $0.00803 |
| Sonnet 5.5 | $0.00003 | $0.00401 |
| Haiku 4.5 | $0.00001 | $0.00201 |
Grade A, and why
retro 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 — 329 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/own:retro
⚠️ PLAN MODE WARNING: Toggle plan mode off before running this command (
shift+tab). OwnYourCode commands don't work correctly with plan mode.
Extract learnings from completed work and persist them for future reference.
Overview
This command is run after completing work (typically after /own:done). It:
- Reflects on what was learned
- Documents patterns worth reusing
- Records failures to avoid
- Updates the learning registry
- Generates skill files for significant learnings
"The junior who documents their failures outgrows the senior who repeats them."
Execution Flow
Phase 1: What Did You Just Complete?
"What did you just finish working on?"
If they just ran /own:done, reference that context.
Get:
- Feature/task name
- Domain (auth, forms, API, etc.)
- Rough summary
Phase 2: Learning Extraction
Ask these questions to extract learnings:
Question 1: The Hard Part
"What was the hardest part of this work?"
Looking for:
- Technical challenges overcome
- Confusing concepts clarified
- Time-consuming debugging
Question 2: The Insight
"What do you know now that you didn't know before you started?"
Looking for:
- New understanding of a concept
- Better approach discovered
- "Aha!" moments
Question 3: The Pattern (if applicable)
"Did you discover or use a pattern that worked well? Something you'd want to reuse?"
Looking for:
- Code patterns worth extracting
- Approaches that solved problems elegantly
- Techniques to remember
Question 4: The Failure (most valuable)
"Did you make any mistakes or hit any walls? What went wrong before it went right?"
Looking for:
- Bugs that took time to find
- Wrong approaches tried first
- Misunderstandings that caused problems
Question 5: The Advice
"If you could go back and tell yourself one thing before starting this task, what would it be?"
This often captures the most actionable learning.
Phase 3: Categorize Learnings
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 · 329 lines · 14 tokens per session scan A 345590b896b6
retro is a command published in the GitHub repository DanielPodolsky/ownyourcode (292 stars, last pushed 4mo ago), licensed MIT. It adds 14 tokens to every session and 2,007 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-30.
Other commands, from other repositories
ingest
Ingest source material into an active wiki. Accepts URLs, file paths, PDFs, freeform text, or processes the inbox. Supports tweets via Grok MCP.
checkpoint
Export, refresh, verify, or import a comprehensive cross-topic Project Knowledge Checkpoint for a repository, with privacy checks.
retract
Remove user-selected data or a source from wiki-controlled local files, including archives and session context. Dry-run first, apply explicitly, then verify.
session
Capture, list, rehydrate, and promote llm-wiki session context. Supports automated hook capture into HUB/.sessions plus explicit promotion into topic raw notes.
archive
Archive or restore whole topic wikis so old interests stay preserved but out of default context. Archived topics move under HUB/topics/.archive and are hidden from normal semantic and maintenance workflows.
retex
Retex - Capture lesson learned dans memory après fix, rollback, erreur.