Borrowing it
Nothing to install: this file belongs to fulminate-io/knowledge-mcp. 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/fulminate-io/knowledge-mcp/main/.claude/skills/retro/SKILL.mdgit clone --depth 1 https://github.com/fulminate-io/knowledge-mcpWrote 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/fulminate-io/knowledge-mcp/retro)<a href="https://agentmods.dev/skills/fulminate-io/knowledge-mcp/retro"><img src="https://agentmods.dev/badge/skills/fulminate-io/knowledge-mcp/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.00062 | $0.02882 |
| Opus 5 | $0.00031 | $0.01441 |
| Sonnet 5 | $0.00012 | $0.00576 |
| Haiku 4.5 | $0.00006 | $0.00288 |
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 6d 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 — 266 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Retro: $ARGUMENTS
This is the terminal phase of the workflow chain: brainstorm (WHY) → orchestrate (execution) → retro (feedback loop). The main LLM runs it directly — it is NOT a delegating phase that spawns subagents. It runs in the loop that holds the full session context, because only that loop knows what was actually built, what was observed working, and which hypotheses the real-world result confirmed.
For execution-phase discipline reference /orchestrate. For metacognition over the existing thought graph (a different job — see Step 6) reference /reflect.
retro's deliverable: durable, recall-able session knowledge — a reproduction guide future sessions can act on, plus the reasoning validated against what actually happened. The session's thoughts, the broken→fixed evidence, and the "how do I reproduce / test / connect to this" knowledge otherwise live only in scrollback and evaporate. retro writes them into the graph before they are lost.
retro CREATES session artifacts. /reflect ANALYZES the existing thought graph. They are different skills; retro may hand off to /reflect at the end (Step 6).
The following are NOT sufficient evidence on their own — they are the premature
trap, and you must not capture on them alone:
- green unit tests
- plan completion / all phases done
- tickets closed / "implementation finished"
If the precondition does NOT hold, STOP. Say so plainly, name what still needs
to be exercised for real, and do not write the guide. Premature capture is this
skill's cardinal failure.
You are capturing the feedback loop for the work this session delivered. Work through the steps in order. Be concrete and reproducible — the guide is written for a future session (or teammate) who has none of your context.
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.
- 6d ago First seen · 266 lines · 62 tokens per session scan A 670fb3705ab9
retro is a skill published in the GitHub repository fulminate-io/knowledge-mcp (1 stars, last pushed yesterday), licensed Apache-2.0. It adds 62 tokens to every session and 2,882 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…