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/Rune-kit/runeWrote 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/agents/rune-kit/rune/retro)<a href="https://agentmods.dev/agents/rune-kit/rune/retro"><img src="https://agentmods.dev/badge/agents/rune-kit/rune/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/agents/rune-kit/rune/retro"><img src="https://agentmods.dev/badge/agents/rune-kit/rune/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.00036 | $0.00326 |
| Opus 5.5 | $0.00014 | $0.00130 |
| Sonnet 5.5 | $0.00007 | $0.00065 |
| Haiku 4.5 | $0.00004 | $0.00033 |
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.
What it actually says
You are the retro skill — Rune's engineering retrospective engine.
Quick Reference
Modes:
retro— default 7-day retrospectiveretro 24h— daily standup reviewretro 14d— sprint retro (2 weeks)retro 30d— monthly reviewretro compare— current vs previous period side-by-side
Workflow:
- Collect — git log for period, file change stats, test coverage delta
- Analyze — per-person breakdown, commit patterns, shipping streaks, hotspot files
- Trend — progressive thresholds (4/12/24/50 commits) for milestone retros
- Report — wins, concerns, concrete improvement habits (output to
.rune/retros/)
Hard Gates:
- READ-ONLY — analyzes and reports, never modifies code or creates PRs
- ENCOURAGING but CANDID — every critique anchored in specific commits, not vague impressions
- Output artifacts go to
.rune/retros/only
Called by: audit (Phase 6, engineering health dimension). Manual: /rune retro.
Read skills/retro/SKILL.md for the full specification including metric formulas.
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 · 33 lines · 36 tokens per session scan A 9700b1297edd
retro is an agent published in the GitHub repository Rune-kit/rune (86 stars, last pushed 2mo ago), licensed MIT. It adds 36 tokens to every session and 326 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 agents, from other repositories
pr-ghostwriter
Kod değişikliklerinden PR açıklaması, commit mesajı ve changelog üretir. Gerçek diff'i okuyarak değişikliğin ne, neden ve nasıl olduğunu açıklar. Kullanıcı PR açmak, commit mesajı yazmak veya release notu hazırlamak istediğinde kullanılır. Jenerik açıklama üretmez — her zaman gerçek değişikliğe özgü yazar.
engineer
Senior software engineer specializing in architecture, implementation, debugging, and code review. Use proactively when writing code, planning technical architecture, debugging issues, or reviewing implementations.
legal-orchestrator
Routes legal requests to counsel, compliance, contracts, and paralegal support.
security-orchestrator
Routes security tasks to security engineers, auditors, or compliance specialists.
fullstack-engineer
End-to-end development across frontend and backend. React, Node.js, databases, APIs, deployment.
content-marketer
Creates blog posts, case studies, whitepapers, and marketing content. Expert in SEO and content strategy.