retrospective

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/jeremydev87/codingbuddy/retrospective

Any agent

npx skills add JeremyDev87/codingbuddy --skill retrospective

Clone the repo

git clone --depth 1 https://github.com/JeremyDev87/codingbuddy

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/jeremydev87/codingbuddy/retrospective.svg)](https://agentmods.dev/skills/jeremydev87/codingbuddy/retrospective)

Your own site

<a href="https://agentmods.dev/skills/jeremydev87/codingbuddy/retrospective"><img src="https://agentmods.dev/badge/skills/jeremydev87/codingbuddy/retrospective.svg" alt="Measured on agentmods" height="20"></a>

Per session 38 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

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

Security scan A 0 findings. Scan, not verified.

Origin unknown 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	$0.00038	$0.01379
Opus 5	$0.00019	$0.00690
Sonnet 5	$0.00008	$0.00276
Haiku 4.5	$0.00004	$0.00138

Measured today against content hash 797be3925619, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

retrospective 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 today.

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.

packages/rules/.ai-rules/skills/retrospective/SKILL.md · 193 lines

How it starts

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

Session Retrospective

Overview

Analyze accumulated PLAN/ACT/EVAL session data from context archives to surface coding habits, recurring patterns, and actionable improvement suggestions. Transforms passive session history into data-driven growth insights.

Core principle: Decisions improve when informed by patterns, not just memory. Review what actually happened, not what you think happened.

When to Use

After completing a sprint or milestone
During periodic team/personal retrospectives
When noticing repeated issues across sessions
Before planning process improvements
When onboarding to understand team patterns

When NOT to Use

Mid-session (wait until a natural checkpoint)
With fewer than 3 archived sessions (insufficient data)
For real-time debugging (use systematic-debugging instead)

Prerequisites

Context archive system enabled (#999)
At least 3 archived sessions in docs/codingbuddy/archive/
MCP tools available: get_context_history, search_context_archives

Process

Phase 1: Data Collection

Gather session archives and extract structured data.

Retrieve recent archives
- Call get_context_history with appropriate limit (default: 20)
- If no archives exist, inform user and suggest running a few PLAN/ACT/EVAL sessions first
- Note the date range covered
Read archive contents
- Read each archived context document
- Extract from each session:
  - Mode transitions (PLAN, ACT, EVAL, AUTO)
  - Primary agent used
  - Task description and title
  - Decisions made
  - Notes recorded
  - Progress items (ACT mode)
  - Findings and recommendations (EVAL mode)
  - Status (completed, in_progress, blocked)

Phase 2: Pattern Analysis

Analyze collected data across five dimensions.

2a. Mode Usage Patterns

Count sessions per mode (PLAN, ACT, EVAL, AUTO)
Calculate EVAL adoption rate: EVAL sessions / total sessions
Identify sessions that skipped EVAL (potential quality gaps)
Flag AUTO mode usage frequency

Read the full file on GitHub · 193 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.

today First seen · 193 lines · 38 tokens per session scan A 797be3925619

Subscribe to this mod's changes

retrospective is a skill published in the GitHub repository JeremyDev87/codingbuddy (31 stars, last pushed 4mo ago), licensed MIT. It adds 38 tokens to every session and 1,379 once invoked, about $0.0002 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-09-03.

Testing ai-agents ai-coding ai-coding-assistant ai-rules claude-code code-quality

ring:searching-code

Forensic code search and analysis with optional Chain of Draft (CoD) ultra-concise mode. Five-phase methodology (clarification, planning, execution, analysis, synthesis) with severity assessment. Use for targeted investigation of specific patterns, bugs, or vulnerabilities. Skip for broad architecture mapping (use…

LerianStudio/ring · 74 tokens

ring:exploring-codebases

Exploring a codebase across phases: scopes the target, detects architecture, components, and layers, deep-dives each discovered perspective, then synthesizes findings into actionable guidance with file:line evidence. Use to understand how a feature or system works before planning changes, or to orient on an unfamiliar…

LerianStudio/ring · 91 tokens

ring:auditing-dependency-security

Auditing a dependency for supply-chain risk before install (pip/npm/go/cargo): checks typosquatting, maintainer/age risk, vulnerability DBs (OSV, GHSA, Socket), and lockfile hash pinning, then emits a risk score and approve/conditional/escalate/block decision. Use when adding or updating a dependency, reviewing a…

LerianStudio/ring · 102 tokens

ring:checking-frontend-quality

Checking frontend quality against changed UI via ring:qa-frontend in accessibility, visual, e2e, or performance mode and aggregating pass/fail verdicts. Use when a frontend change needs standalone a11y, visual-snapshot, Playwright e2e, or Lighthouse/Core-Web-Vitals validation outside the dev cycle. Skip for…