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 skills/floomhq/moto/retronpx skills add floomhq/moto --skill retrogit clone --depth 1 https://github.com/floomhq/motoWrote 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/skills/floomhq/moto/retro)<a href="https://agentmods.dev/skills/floomhq/moto/retro"><img src="https://agentmods.dev/badge/skills/floomhq/moto/retro.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.00064 | $0.00569 |
| Opus 5 | $0.00032 | $0.00284 |
| Sonnet 5 | $0.00013 | $0.00114 |
| Haiku 4.5 | $0.00006 | $0.00057 |
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 5d 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.
What it actually says
Retro Skill
Purpose
A retrospective identifies what worked, what didn't, and how to improve. It's not a blame exercise - it's a learning exercise.
Step 1: Gather context
Ask (if not already clear):
- What time period or project are we retrospecting?
- Were there specific goals set at the start?
- Are there any standout events (wins, blockers, incidents) to discuss?
Step 2: Review what happened
Look at evidence from the period:
# Review recent commits
git log --oneline --since="1 week ago"
# Review closed issues
gh issue list --state closed --limit 20
# Review PRs merged
gh pr list --state merged --limit 20
Step 3: Structure the retro
What went well
- Accomplishments: what was shipped, completed, or improved
- Practices that worked: processes, tools, approaches that helped
- Unexpected wins
What didn't go well
- Blocked or delayed items
- Technical debt incurred
- Communication gaps
- Estimates that were off
Surprises
- Things that took longer than expected (and why)
- Things that were easier than expected
- External factors that changed the plan
Learnings
- What would be done differently?
- What was learned about the codebase, users, or process?
- What assumptions were proven wrong?
Step 4: Action items
For each identified issue, generate a concrete action item:
ACTION ITEMS:
1. [Problem] → [Action] → [Owner] → [By when]
2. [Problem] → [Action] → [Owner] → [By when]
Action items must be:
- Specific (not "improve testing" but "add integration tests for auth flow")
- Achievable (can be done in the next sprint)
- Owned (someone is responsible)
Output Format
RETRO: [Period]
Date: [Today]
WINS
- [win 1]
- [win 2]
DIDN'T GO WELL
- [issue 1]
- [issue 2]
SURPRISES
- [surprise 1]
LEARNINGS
- [learning 1]
- [learning 2]
ACTION ITEMS
- [ ] [action 1]
- [ ] [action 2]
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.
- 5d ago First seen · 100 lines · 64 tokens per session scan A 51f5f96f12b6
retro is a skill published in the GitHub repository floomhq/moto (32 stars, last pushed 2mo ago), licensed MIT. It adds 64 tokens to every session and 569 once invoked, about $0.0003 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-30.
Other skills, from other repositories
issue-triage
Issue triage: audit open issues, categorize, detect duplicates, cross-ref PRs, risk assessment, post comments. Args: "all" for deep analysis of all, issue numbers to focus (e.g. "42 57"), "en"/"fr" for language, no arg = audit only in French.
performance
CLI performance optimization - startup time, memory usage, token savings benchmarking.
build-teaql-app
Build or change a TeaQL application in Java, Rust, Go, Swift, Python, C#/.NET, or TypeScript, including Kotlin/JVM applications that consume Java-generated libraries. Mandatory order: first draft and save a complete KSML model, then verify the client and evaluate that saved model, repair it through repeated evaluation…
moai-workflow-worktree
Git worktree management for parallel SPEC development with isolated workspaces, automatic branch registration, and seamless MoAI-ADK integration. Use when setting up parallel development environments.
moai-kanban-foreman
One unattended kanban foreman iteration: watch the backlog queue, dispatch the next operator-picked card to an isolated worker, collect completion evidence on read (not on claims), and report. This is the body the project's loop.md driver invokes each iteration of a bare /loop; it can also be invoked directly to test…
moai-domain-uiux
UI/UX design systems specialist covering accessibility, icons, theming, design tokens, and user experience patterns. Use when working on design systems, WCAG compliance, ARIA patterns, or dark mode theming.