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.
npx agentmods add skills/botminter/botminter/retrospectivenpx skills add botminter/botminter --skill retrospectivegit clone --depth 1 https://github.com/botminter/botminterWrote 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/botminter/botminter/retrospective)<a href="https://agentmods.dev/skills/botminter/botminter/retrospective"><img src="https://agentmods.dev/badge/skills/botminter/botminter/retrospective.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.00077 | $0.01559 |
| Opus 5 | $0.00039 | $0.00779 |
| Sonnet 5 | $0.00015 | $0.00312 |
| Haiku 4.5 | $0.00008 | $0.00156 |
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 5d 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 — 199 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Retrospective Skill
Guide a structured retrospective conversation, gather data from the project board, and produce a retro summary with typed action items.
When to Use
- An
cos:exec:todoissue requests a retrospective - The operator asks to reflect on a sprint, milestone, or time period
- You want to identify improvement opportunities from completed work
Procedure
Step 1: Define Scope
Determine what period the retro covers:
- Milestone-based: A specific milestone (e.g., "v0.5 retrospective")
- Time-based: A date range (e.g., "last two weeks")
- Epic-based: A specific epic or feature area
Ask the operator or read the issue body to clarify the scope.
Step 2: Gather Board Data
Query the project board for completed work within the retro scope.
# Use the github-project skill's query-issues operation
# By milestone:
# query-issues --type milestone --milestone "<milestone>"
# By status:
# query-issues --type status --status "done"
Gather these data points:
- Completed issues: Count and list of closed issues in scope
- Rejection loops: Count comments matching
"Changes requested"or"review.changes_requested"patterns per issue — multiple rounds indicate friction - Error statuses: Issues that hit
errorstatus (check forstatus/errorlabel or project status field) - Long-lived in-progress: Issues that stayed in
*:in-progressfor more than 2x the average cycle time - Cycle time: Time from
*:todoto*:donefor each issue
Step 3: What Went Well
Identify patterns of success from the data:
- Issues completed quickly (below-average cycle time)
- Clean reviews (0-1 review rounds)
- Good designs that led to smooth implementation
- Effective collaboration patterns visible in comments
- Knowledge or tooling improvements that paid off
Document each positive pattern with supporting evidence (issue numbers, metrics).
Step 4: What Didn't Go Well
Identify pain points and improvement areas:
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.
- 5d ago First seen · 199 lines · 77 tokens per session scan A fa780f8c7c18
retrospective is a skill published in the GitHub repository botminter/botminter (18 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 77 tokens to every session and 1,559 once invoked, about $0.0004 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.
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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…