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 skills add helderberto/agent-skills --skill retrogit clone --depth 1 https://github.com/helderberto/agent-skillsWrote 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/helderberto/agent-skills/retro)<a href="https://agentmods.dev/skills/helderberto/agent-skills/retro"><img src="https://agentmods.dev/badge/skills/helderberto/agent-skills/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/helderberto/agent-skills/retro"><img src="https://agentmods.dev/badge/skills/helderberto/agent-skills/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.00022 | $0.00728 |
| Opus 5.5 | $0.00009 | $0.00291 |
| Sonnet 5.5 | $0.00004 | $0.00146 |
| Haiku 4.5 | $0.00002 | $0.00073 |
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 4d 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 — 40 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Retro
Look back over a session and suggest changes to the agent's environment — navigation pointers, automated checks, coding standards, steering files, tooling — so the next run starts from a better place. Apply nothing until the user picks.
Steps
- Read the session. Default: this one, before
/clear. An earlier session ($ARGUMENTS) lives at~/.claude/projects/<cwd with / as ->/<session-id>.jsonl. Redact secrets when you quote it. - Read the environment first:
CLAUDE.md/AGENTS.md(repo and global),CODING_STANDARDS.md, the repo's own lint / typecheck / test commands, pre-commit hooks, CI workflows. - Find candidates in every category below. Completion: each category has a candidate or "nothing found".
- Present them most severe first, each with its session evidence (what happened, where) and the proposed change. Apply only what the user picks. Before drafting steering text, call the Skill tool with
create-skillfor its Writing style: the no-op test, prompt the positive.
Categories
- Navigation — the session took long to find a file or fact → a navigation pointer.
- Automated checks — a mistake a check could have caught, or no guardrail at all (no pre-commit hook, no CI job running lint / types / tests). A check that exists but sits unwired or silently broken is the finding, not a new one.
- Coding standards — the reviewer missed a mistake, or a rule needs removing or clarifying. Classify first. Mechanical (syntactic pattern, banned API, import shape, file location) → a deterministic check: lint rule, hook, or CI job, whichever the repo's guardrail makes cheapest. Judgment call →
CODING_STANDARDS.md. - Global AGENTS.md — steering in
CLAUDE.md/AGENTS.md(repo or global) that belongs in a standard or a check. - Tool economy — expensive or token-heavy calls a cheaper call or script would replace.
- No-ops — steering lines that don't change behavior.
- Information access — what the agent lacked: dev-server logs, read-only access to a third-party service.
- Bug prevention — after
/debug: what would have prevented the bug? No good test seam, tangled callers, hidden coupling → the candidate is an architecture audit with those specifics.
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.
- 4d ago Changed · +2 lines 2d564728c015
- 7d ago First seen · 38 lines · 22 tokens per session scan A 9c54ca637c01
retro is a skill published in the GitHub repository helderberto/agent-skills (17 stars, last pushed 3d ago), licensed MIT. It adds 22 tokens to every session and 728 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-10-09.
Other skills, from other repositories
interview-me
An interview skill that asks one question at a time to uncover what a user actually needs. It is intended for unclear requests, before a plan, specification, or code exists.
meeting-notes-to-tasks
Converts unstructured meeting notes into structured, assigned, time-bounded action items. Never leave a meeting without knowing who does what by when.
claude-session
Find and inspect local Claude Code conversations by session GUID, title, phrase, or recent activity. Use when the user runs /claude-session, asks what Claude Code work they have been doing lately, says a Claude Code conversation died, ran out of context, crashed, or exhausted usage, wants to resume a named…
Send WhatsApp text or media with the local wacli linked-device CLI when the user invokes /whatsapp or explicitly asks to send a WhatsApp message.
bash
Expert Bash shell scripting assistance covering POSIX compliance, parameter expansion, pipelines, traps, and debugging. Use when writing robust shell scripts, automating DevOps tasks, or handling file processing.
uninstall
Uninstall a community skill that was installed via the hub. Confirms before deleting files, refuses to touch first-party plugin skills, and logs every action. Use when the user wants to fully remove a community skill ("uninstall [skill]", "remove this skill") rather than just disable it.