Borrowing it
Nothing to install: this file belongs to Lengros/bennu. 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/Lengros/bennu/main/.claude/skills/retro/SKILL.mdgit clone --depth 1 https://github.com/Lengros/bennuWrote 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/lengros/bennu/retro)<a href="https://agentmods.dev/skills/lengros/bennu/retro"><img src="https://agentmods.dev/badge/skills/lengros/bennu/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/skills/lengros/bennu/retro"><img src="https://agentmods.dev/badge/skills/lengros/bennu/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.00054 | $0.03040 |
| Opus 5.5 | $0.00022 | $0.01216 |
| Sonnet 5.5 | $0.00011 | $0.00608 |
| Haiku 4.5 | $0.00005 | $0.00304 |
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 2mo 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 — 226 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/retro — LEARN-loop consumer
When to run
telemetry/retro.flagexists in this project (session-start.sh injects its content; CLAUDE.md startup reads it as fallback).- Monthly cadence:
session-end.shalso setsretro.flagwhen the lasttype:"retro"marker is >30 days old (or, with no retro ever, the oldest activity is >30d), so the loop turns even in a low-friction month. No external cron — the calendar check rides the existing flag mechanism.
Arguments: none.
Parsing discipline — read before any step
Parse every telemetry line with a real JSON parser (python3 -c 'json.loads(...)'
or jq), then match on the parsed type field. Never select records by
string-matching "type":"run" with grep, and never field-split on a "key":"
literal (e.g. awk -F'"ts":"'). The corpus is NOT uniformly formatted: log-run.sh
historically emitted spaced JSON ({"ts": "...", "type": "run", ...}) while the hooks
emit compact JSON ({"ts":"...","type":"..."}). A string-matcher keyed on the compact
shape silently drops every run record — which produces a false "0 runs / R2,R3,reuse
unmeasurable" report even when dozens of runs exist (this exact failure occurred 2026-06-13).
json.loads is whitespace-agnostic and reads both shapes; that is the only safe reader.
The two "type":"..." and ts >= window_start comparisons named in the steps below are
logical predicates over parsed objects, not grep patterns.
Step 1 — Determine the review window
Read telemetry/runs.jsonl and parse each line as JSON (see Parsing discipline above).
Scan all parsed records for type == "retro" events.
The session-end record shape is defined in
[Observed: .claude/hooks/session-end.sh:93-95].
Take the most recent one's ts field as window_start. If none found, set
window_start = now − 30 days. Also record prior_retro_ts = the second-most-recent
type:"retro" ts if one exists (consumed by the skip-rate watch in section d); if there are
fewer than two retro markers, prior_retro_ts is undefined.
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.
- 2mo ago First seen · 226 lines · 54 tokens per session scan A cc8683033fa3
retro is a skill published in the GitHub repository Lengros/bennu (2 stars, last pushed 3mo ago), licensed MIT. It adds 54 tokens to every session and 3,040 once invoked, about $0.0002 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-31.
Other skills, from other repositories
kanban-video-orchestrator
Plan and run multi-agent video production pipelines.
sdlc-review
Review Kanban handoffs and route verified outcomes.
teams-meeting-pipeline
Teams meeting summaries, job replay, Graph subscriptions.
module-governance
Establish or maintain a business module's local agent instructions, domain-context links, and interface ownership when implementing a new module or changing its responsibilities. Reuse project-level rules and existing ECC workflows; ordinary bug fixes, styling, and read-only design discussions do not start module…
docs-governance
Route broad documentation-governance requests to existing ECC skills and run an opt-in, read-only audit of mapped documentation roles, links, ADR indexes, and evidence references. Use when a user asks for documentation governance, project-knowledge organization, documentation integrity, or a deterministic docs audit…
context-and-decisions
Govern stable domain context with a narrowly scoped CONTEXT.md when needed, and route hard-to-reverse decisions to ECC's existing architecture-decision-records skill. Use when domain terms require repeated explanation, one term has multiple meanings, unclear language causes module-boundary mistakes, or domain…