lesson-retro

lesson-retro is a skill for Claude Code, Codex from mshadmanrahman/claudecode-guide. It costs 63 tokens per session (683 once invoked), scanned A, original, MIT.

A review method that turns student feedback from a past class or course run into a checked list of changes for the next one. It compares the feedback with the plan students actually received.

In plain words
What is it for?
Analysing CSV exports, survey responses, or notes; calculating rating summaries; identifying recurring problems; and drafting changes for the next course run.
Why use it?
It prevents decisions based only on impressions by requiring counts, low-score details, and differences between batches or survey methods. It also keeps the teacher responsible for the final choices.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Analysing CSV exports, survey responses, or notes; calculating rating summaries; identifying recurring problems; and drafting changes for the next course run.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/mshadmanrahman/claudecode-guide/lesson-retro
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.

Any agent
npx skills add mshadmanrahman/claudecode-guide --skill lesson-retro
Clone the repo
git clone --depth 1 https://github.com/mshadmanrahman/claudecode-guide

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 lesson-retro

README.md
[![agentmods](https://agentmods.dev/badge/skills/mshadmanrahman/claudecode-guide/lesson-retro/github.svg)](https://agentmods.dev/skills/mshadmanrahman/claudecode-guide/lesson-retro)
Your own site
<a href="https://agentmods.dev/skills/mshadmanrahman/claudecode-guide/lesson-retro"><img src="https://agentmods.dev/badge/skills/mshadmanrahman/claudecode-guide/lesson-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.

agentmods 80×15 button for lesson-retro

Your own site · 80×15
<a href="https://agentmods.dev/skills/mshadmanrahman/claudecode-guide/lesson-retro"><img src="https://agentmods.dev/badge/skills/mshadmanrahman/claudecode-guide/lesson-retro.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 63 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 683 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00063 $0.00683
Opus 5.5 $0.00025 $0.00273
Sonnet 5.5 $0.00013 $0.00137
Haiku 4.5 $0.00006 $0.00068

Measured 6d ago against content hash 8aef87ffbb00, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

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

public/skills/lesson-retro/SKILL.md · 66 lines

How it starts

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

Lesson retro

You help a teacher improve the next run of a course using what the last run's students said. The teacher decides. You count, check and draft.

Ask for these first

Do not start until you have all three. Ask for whichever is missing.

  1. The feedback. A spreadsheet export (CSV), pasted survey rows, or typed notes.
  2. The last plan. The lesson plan, outline or schedule the students actually got.
  3. What cannot change. Fixed things: class length, platform rules, required quizzes, dates.

Step 1: Count, and show the working

  • Give the average for every numeric rating as a sum over a count, for example 9.22 = 166/18.
  • Give the lowest score and how many people gave it.
  • If the scores come from more than one batch, report each batch on its own line.
  • If two batches were collected differently (a phone call versus a self-filled form, a word scale versus 1 to 10), say so and do not compare them as numbers.
  • Say how many people answered. A small count is a fact to state, not a reason to skip the work.

Step 2: Read the low scores first

  • List every response at the bottom of the scale with its comment and date.
  • Note when the low scores arrived. Low scores bunched on the first day often describe a first impression, not the whole course.
  • Summarize each complaint in plain words. Never repeat a student's name, phone number or email.

Step 3: Check each complaint before changing anything

For each complaint, ask the teacher one question that would prove or disprove it, then wait.

  • "Class runs too long" is checked against real start and end times.
  • "Too hard" is checked against how many students submitted the related assignment.
  • "Not useful" is checked against which parts students said they used.

Mark each complaint as confirmed, not confirmed or can't tell yet, with the evidence. Only confirmed complaints become changes.

Step 4: Write the change table

What the evidence showed Change for next time How we'll know it worked

Read the full file on GitHub · 66 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. 6d ago First seen · 66 lines · 63 tokens per session scan A 8aef87ffbb00

Subscribe to this mod's changes

lesson-retro is a skill published in the GitHub repository mshadmanrahman/claudecode-guide (45 stars, last pushed 2d ago), licensed MIT. It adds 63 tokens to every session and 683 once invoked, about $0.0003 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-31.

Related

lesson-retro compared with skills from other repositories

lesson-retro next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
lesson-retromshadmanrahman/claudecode-guideSkill452d agoMITA63Claude Code, Codex
career-path-plannertravisjneuman/.claudeSkill107yesterdayMITA41Claude Code, Codex
case-interview-practicetravisjneuman/.claudeSkill107yesterdayMITA39Claude Code, Codex
debate-practice-coachtravisjneuman/.claudeSkill107yesterdayMITA45Claude Code, Codex
onboarding-guide-creatortravisjneuman/.claudeSkill107yesterdayMITA37Claude Code, Codex
course-material-creatortravisjneuman/.claudeSkill107yesterdayMITA40Claude Code, Codex
learning-gap-analyzertravisjneuman/.claudeSkill107yesterdayMITA36Claude Code, Codex