agentmods.dev

session-retro

session-retro is a skill for Claude Code, Codex from dentiny/kon. It costs 56 tokens per session (946 once invoked), scanned A, original, MIT.

A session wrap-up guide for proposing evidence-based lessons from an agent work session for later memory, with human confirmation before saving them.

In plain words
What is it for?
Use it at the end of supported multi-step workflows to review session learnings, propose memory entries, and save them only after confirmation.
Why use it?
It helps preserve useful working conventions without automatically recording guesses or unapproved information.

Skill for Claude CodeCodex

not rated 3 1mo ago A scan 56 tokens original MIT
View the source file dentiny/kon
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.

agentmods
npx agentmods add skills/dentiny/kon/session-retro
Any agent
npx skills add dentiny/kon --skill session-retro
Clone the repo
git clone --depth 1 https://github.com/dentiny/kon

Made for: Claude Code, Codex.

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.

agentmods badge for session-retro

README.md
[![agentmods](https://agentmods.dev/badge/skills/dentiny/kon/session-retro.svg)](https://agentmods.dev/skills/dentiny/kon/session-retro)
Your own site
<a href="https://agentmods.dev/skills/dentiny/kon/session-retro"><img src="https://agentmods.dev/badge/skills/dentiny/kon/session-retro.svg" alt="Measured on agentmods" height="20"></a>
Per session 56 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 946 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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.

ModelPer sessionOnce invoked
Fable 5 $0.00056 $0.00946
Opus 5 $0.00028 $0.00473
Sonnet 5 $0.00011 $0.00189
Haiku 4.5 $0.00006 $0.00095

Measured 3d ago against content hash d385d623e427, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

session-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 3d 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.

skills/session-retro/SKILL.md · 86 lines

How it starts

The opening of the file, as written. The whole thing — 86 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Session Retro

Owner: orchestrator (no Task subagents) Consumers: /kon:team, /kon:quick, /kon:design, /kon:debug, /kon:gc, /kon:address-comments. Optional manual re-run: /kon:retro.

Core principles (always): follow skills/core-principles — propose only evidence-backed lessons; don't invent retro insights.

Save paths

Saving is always:

  1. Mid-session — Mio/Yui ## Memory propose → confirm → write
  2. End of pipeline — retro (below) → confirm → write

To browse stored entries, read the indexes directly:

cat ~/.kon/public/memory/MEMORY.md
cat ~/.kon/projects/<repo-name>/memory/MEMORY.md

When to run

Default session close for pipeline commands (after work + Mio approve + /kon:summarize):

summarize → retro → user /kon:finish or dashboard ✓

Skip retro for read-only commands: /kon:ask, /kon:review, /kon:review-pr, /kon:research, /kon:describe-issue, /kon:todo.

User may say skip retro to close without proposing.

Candidate sources (≤ 5)

Scan conversation + session artefacts:

  • Explicit user prefs / feedback ("always integration tests", "shorter reviews")
  • Conventions agreed this session (commit style, test naming)
  • Lessons / pitfalls ("lib X differs on macOS")
  • Skipped ## Memory propose sections from Mio/Yui this session (re-offer)
  • Plan ## Honoured memory or debug notes worth persisting

Exclude: one-off task facts, ticket numbers, secrets, .env values, API keys.

Flow

  1. Collect ≤ 5 candidates — rank by reuse signal; drop lowest if > 5.
  2. Zero candidates → print "Nothing to propose for memory." and exit retro.
  3. One at a time — for each candidate:
    • Print Candidate i/N: quote + inferred type, name, description, suggested scope (public or repo).
    • Ask: Save to public / Save to repo / Edit / Skip / Done with retro.
    • On save/edit → run skills/memory-propose-confirm write steps.
  4. Summary — list saved entries with scope, or "Retro complete — nothing saved."

Read the full file on GitHub · 86 lines

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.

  1. 3d ago First seen · 86 lines · 56 tokens per session scan A d385d623e427

Subscribe to this mod's changes

session-retro is a skill published in the GitHub repository dentiny/kon (3 stars, last pushed 1mo ago), licensed MIT. It adds 56 tokens to every session and 946 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.

Memory and context
Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

obra/superpowers · 37 tokens

auto-perf-optimize

Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.

microsoft/vscode · 62 tokens

chat-perf

Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.

microsoft/vscode · 51 tokens

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.

microsoft/vscode · 53 tokens

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…

microsoft/vscode · 71 tokens