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/CES-Ltd/LumiWrote 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/ces-ltd/lumi/octo-retro)<a href="https://agentmods.dev/commands/ces-ltd/lumi/octo-retro"><img src="https://agentmods.dev/badge/commands/ces-ltd/lumi/octo-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/ces-ltd/lumi/octo-retro"><img src="https://agentmods.dev/badge/commands/ces-ltd/lumi/octo-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.00012 | $0.01477 |
| Opus 5 | $0.00006 | $0.00739 |
| Sonnet 5 | $0.00002 | $0.00295 |
| Haiku 4.5 | $0.00001 | $0.00148 |
Grade A, and why
octo-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 11d 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.
This is a copy
88% identical to octo-retro — 5 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 207 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Retro — Engineering Retrospective from Git History
Your first output line MUST be: 🐙 Octopus Retrospective
Generate data-driven engineering retrospectives by mining git history. Surfaces commit patterns, contributor breakdown, hotspots, session analysis, and AI-assisted commit tracking.
Usage
/octo:retro # Last 7 days (default)
/octo:retro 24h # Last 24 hours
/octo:retro 14d # Last 14 days
/octo:retro 30d # Last 30 days
Instructions
When the user invokes /octo:retro, you MUST follow these steps exactly.
1. Parse Time Window
Accept an optional argument for the time window. Default to 7d if none provided.
Supported formats:
24h— last 24 hours (--since='24 hours ago')7d— last 7 days (--since='7 days ago')14d— last 14 days (--since='14 days ago')30d— last 30 days (--since='30 days ago')
Map the argument to a git --since value. If the argument does not match a supported format, warn the user and fall back to 7d.
2. Gather Git Data
Run the following git commands to collect raw data. Each command MUST be executed — do NOT skip any.
Commit list:
git log --oneline --since='<window>' --no-merges
LOC changes (lines added/removed per file):
git log --numstat --since='<window>' --no-merges --format=''
Contributor leaderboard:
git shortlog -sn --since='<window>' --no-merges
Hotspot analysis (files modified most often):
git log --format='' --name-only --since='<window>' --no-merges | sort | uniq -c | sort -rn | head -20
PR merge count (merge commits):
git log --oneline --since='<window>' --merges | wc -l
Commit timestamps for session detection:
git log --format='%at %H %s' --since='<window>' --no-merges
AI-assisted commit detection:
git log --since='<window>' --no-merges --format='%H' | xargs -I{} git log -1 --format='%b' {} | grep -ci 'Co-Authored-By:'
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.
- 11d ago First seen · 207 lines · 12 tokens per session scan A 1b706d8d86b1
octo-retro is a command published in the GitHub repository CES-Ltd/Lumi (31 stars, last pushed 4mo ago), licensed MIT. It adds 12 tokens to every session and 1,477 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 88% identical to octo-retro, differing in 5 lines, and is treated as a copy.
Other commands, from other repositories
revert
Git-aware undo by logical work unit (track, phase, or task).
commit-push-pr
An automated Git workflow that checks a project, synchronizes documentation, commits changes, and can create or merge a GitHub pull request. A pull request is a request for teammates to review and add changes to a shared codebase.
auto
An automated coding workflow runs a software task from planning through code changes, checks, and a pull request. A pull request is a proposed change for review before it is merged into the main codebase.
sync
A command that pulls the latest code from the main Git branch and updates the project's key planning and instruction documents to match it.
pull
A quick command that downloads the latest commits from the main Git branch into the current project.
worktree-cleanup
A command for removing a Git worktree, which is a separate working folder linked to the same repository, after its pull request is merged.