A command that saves one important lesson from the current coding task as a Markdown page in a project wiki. It links the new page to related wiki pages so future sessions can find it.

Use it after finishing work to record a design decision, debugging pattern, or other reusable insight in the wiki.

It prevents useful decisions and non-obvious lessons from being lost when a task ends. The saved notes can be recalled later instead of rediscovered.

wiki-retro — Command for Claude Code by zosmaai

Install

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.

Clone the repo

git clone --depth 1 https://github.com/zosmaai/pi-llm-wiki

Made for: Claude Code.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/zosmaai/pi-llm-wiki/wiki-retro/github.svg)](https://agentmods.dev/commands/zosmaai/pi-llm-wiki/wiki-retro)

Your own site

<a href="https://agentmods.dev/commands/zosmaai/pi-llm-wiki/wiki-retro"><img src="https://agentmods.dev/badge/commands/zosmaai/pi-llm-wiki/wiki-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.

Your own site · 80×15

<a href="https://agentmods.dev/commands/zosmaai/pi-llm-wiki/wiki-retro"><img src="https://agentmods.dev/badge/commands/zosmaai/pi-llm-wiki/wiki-retro.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 25 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 382 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00025	$0.00382
Opus 5	$0.00013	$0.00191
Sonnet 5	$0.00005	$0.00076
Haiku 4.5	$0.00003	$0.00038

Measured 10d ago against content hash 064810beb848, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

wiki-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 10d 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.

commands/wiki-retro.md · 36 lines

What it actually says

/wiki-retro

Save an atomic insight from a completed task into the wiki.

Captures what you learned as a single markdown file so that layered recall surfaces it in future sessions.

User Arguments

$ARGUMENTS

Read the LLM Wiki skill at .pi/skills/llm-wiki/SKILL.md first to understand the wiki conventions.

Steps

Identify the key insight(s) from the current task — non-obvious learnings, patterns, or decisions worth preserving
For each insight, call wiki_retro with:
- slug: unique kebab-case identifier (e.g., jwt-revocation-pattern)
- title: short descriptive phrase, ≤60 chars, noun phrase not a sentence
- body: markdown explanation with [[wikilinks]] to related wiki pages
- category: optional (frontend, architecture, devops, bugfix, design, etc.)
Confirm the insight was saved and will be surfaced by layered recall in future sessions
If the insight relates to existing wiki pages, update those pages with cross-references

Rules:

One atomic insight per wiki_retro call. Use multiple calls for multiple insights.
Don't save obvious things. Save non-obvious patterns, tradeoffs, and design decisions.
Always add [[wikilinks]] to connect the new insight with existing wiki knowledge.
Inside Markdown table cells, write aliased wikilinks as [[target\|alias]], never [[target|alias]].

Changes

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.

10d ago First seen · 36 lines · 25 tokens per session scan A 064810beb848

Subscribe to this mod's changes

wiki-retro is a command published in the GitHub repository zosmaai/pi-llm-wiki (566 stars, last pushed today), licensed MIT. It adds 25 tokens to every session and 382 once invoked, about $0.0001 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-30.

Memory and context karpathy knowledge-base llm-wiki markdown obsidian

wiki-retro

Getting it into your agent

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

What it actually says

/wiki-retro

User Arguments

Steps

What this file has done since we first saw it

Other commands, from other repositories

build

lint

ask

load

init_newbrain

vault_gc