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 skills add KirKruglov/claude-skills-kit --skill retro-pattern-analyzergit clone --depth 1 https://github.com/KirKruglov/claude-skills-kitWrote 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/kirkruglov/claude-skills-kit/retro-pattern-analyzer)<a href="https://agentmods.dev/skills/kirkruglov/claude-skills-kit/retro-pattern-analyzer"><img src="https://agentmods.dev/badge/skills/kirkruglov/claude-skills-kit/retro-pattern-analyzer/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.
<a href="https://agentmods.dev/skills/kirkruglov/claude-skills-kit/retro-pattern-analyzer"><img src="https://agentmods.dev/badge/skills/kirkruglov/claude-skills-kit/retro-pattern-analyzer.svg" alt="Reviewed on agentmods" width="80" 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.00078 | $0.01808 |
| Opus 5 | $0.00039 | $0.00904 |
| Sonnet 5 | $0.00016 | $0.00362 |
| Haiku 4.5 | $0.00008 | $0.00181 |
Grade A, and why
retro-pattern-analyzer 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 9d 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 — 163 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Retro Pattern Analyzer
This skill analyzes retrospective files from multiple sprints and produces a structured report identifying recurring pain points, unresolved action items, and stable positive patterns. It reads .md and .txt files, normalizes different retro formats, and outputs retro-patterns-YYYY-MM-DD.md.
Input:
- 2 or more retrospective files in
.mdor.txtformat - Optional: folder path or list of file paths
- Optional: focus area (e.g., "technical issues only", "delivery problems")
Output:
retro-patterns-YYYY-MM-DD.md— structured report with three blocks: recurring pains, unresolved action items, positive patterns
Language Detection
Detect the user's language from their message:
- If Russian (or contains Cyrillic): respond in Russian
- If English (or other Latin-script language): respond in English
- If ambiguous: respond in the language of the trigger phrase used
Instructions
Step 1: Validate Input
-
Check that at least 2 files are provided
- If only 1 file provided: stop. Report: "Pattern analysis requires at least 2 retrospective files. Please provide a second file or folder path."
- If folder path given: list all
.mdand.txtfiles in the folder; if fewer than 2 found, stop with same message
-
Check each file is readable
- If any file is unreadable or path does not exist: skip that file, report: "File [name] not found or unreadable — excluded from analysis."
- Continue with remaining files if at least 2 remain
-
If optional focus area provided: note it; use it to filter themes in Step 3
Step 2: Parse Retrospective Files
- For each file, identify structural sections using keyword detection:
- What went wrong / Problems / Improvements / Minuses / Keep Stop Start →
went-wrongbucket - What went well / Strengths / Positives / Pluses →
went-wellbucket - Action items / Next steps / TODOs / Agreements →
actionsbucket - Russian equivalents: Что мешало / Проблемы / Минусы →
went-wrong; Что помогло / Плюсы →went-well; Договорённости / Задачи →actions
- What went wrong / Problems / Improvements / Minuses / Keep Stop Start →
What ships with it
5 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 9d ago First seen · 163 lines · 78 tokens per session scan A 10555e7ebf5c
retro-pattern-analyzer is a skill published in the GitHub repository KirKruglov/claude-skills-kit (18 stars, last pushed 1mo ago), licensed MIT. It adds 78 tokens to every session and 1,808 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
github-issue-creator
Turn error logs, screenshots, voice notes, and rough bug reports into crisp, developer-ready GitHub issues with repro steps, impact, and evidence.
multi-role-quality-synthesis
Use this skill when multiple role reports for one quality stage must be combined into a traceable synthesis; triggers include multi-role quality synthesis, role report consolidation, disagreement summary..
project-delivery-perspective
Use this skill when project delivery constraints or action tracking are needed for test strategy, test strategy review, or test report review; triggers include project delivery perspective, delivery planning, schedule and capacity..
onboarding-planner
TRIGGER THIS when preparing for new hires, planning first-day/week/month activities, creating onboarding schedules, building 30-60-90 day plans, designing welcome programs, organizing training schedules, or setting up buddy/mentorship programs. Designs comprehensive, engaging onboarding experiences that accelerate…
performance-review-assistant
TRIGGER THIS when conducting performance reviews, writing manager feedback, creating self-assessments, building peer feedback, developing PIPs, creating development plans, or handling difficult performance conversations. Helps write constructive, specific, actionable feedback that develops performance and documents…
sprint-testing-workflow
Use this skill when you need a sprint-based QA workflow from planning through review and retrospective; triggers include sprint testing workflow and iteration QA workflow.