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 commands/ngocsangyem/meowkit/retrogit clone --depth 1 https://github.com/ngocsangyem/MeowKitWrote 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/commands/ngocsangyem/meowkit/retro)<a href="https://agentmods.dev/commands/ngocsangyem/meowkit/retro"><img src="https://agentmods.dev/badge/commands/ngocsangyem/meowkit/retro.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 | $0.00000 | $0.00525 |
| Opus 5 | $0.00000 | $0.00262 |
| Sonnet 5 | $0.00000 | $0.00105 |
| Haiku 4.5 | $0.00000 | $0.00052 |
Grade A, and why
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 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.
How it starts
The opening of the file, as written. The whole thing — 61 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/retro — Sprint Retrospective
Usage
/retro [optional: sprint name or date range]
Behavior
Generates a sprint retrospective by analyzing git history, review findings, and accumulated lessons.
Execution Steps
-
Analyze git log for the period. If a date range or sprint name is provided, scope to that period. Otherwise, use the last 2 weeks. Extract:
- Commits by author
- Branches merged
- Files most frequently changed
-
Summarize activity:
- Features shipped (from
feat:commits) - Bugs fixed (from
fix:commits) - PRs merged (count and titles)
- Review findings (from verdict files in
tasks/reviews/) - Security issues found and resolved
- Features shipped (from
-
Read topic files in
.meowkit/memory/for patterns. Loadfixes.jsonfirst (fall back tofixes.mdif absent),review-patterns.jsonfirst (fall back toreview-patterns.mdif absent), andarchitecture-decisions.jsonfirst (fall back toarchitecture-decisions.mdif absent) — see.claude/rules/memory-read-rules.md. Look for:- Recurring issues (same type of bug appearing multiple times)
- Process friction points noted in lessons
- Things that were learned and applied (or not applied)
-
Generate retro report with three sections:
What went well:
- Features delivered on time
- Clean reviews (all PASS)
- Good test coverage
- Lessons applied from previous retros
What didn't go well:
- Bugs that escaped to production
- Review findings that could have been caught earlier
- Repeated issues across topic files that weren't addressed
- Slow areas (long time between plan and ship)
Action items:
- Specific, actionable improvements
- Assign to a person or process
- Include deadline or trigger condition
-
Propose process improvements. Based on patterns observed, suggest concrete changes to the workflow, rules, or tooling.
-
Write report to:
docs/retros/YYMMDD-retro.md
Output
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 · 61 lines · 0 tokens per session scan A 36ce859ef716
retro is a command published in the GitHub repository ngocsangyem/MeowKit (14 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 525 tokens. 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.
Other commands, from other repositories
project-recap
Generate a visual project recap for context switching.
os-meeting
快速创建和管理AI团队会议.
workspace
Testany Workspace, 管理工作空间，成员权限，团队组织.
standup
Show a daily standup summary with completed, in-progress, and blocked tasks across all active epics.
m-task-planner
Target: $ARGUMENTS (Default: requirement document(s) discovered in the project).
triage
Triage ServiceNow incidents — list open incidents, assess priority, investigate a specific INC, or analyze trends.