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.
git clone --depth 1 https://github.com/fatihkan/badiWrote 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/fatihkan/badi/retro)<a href="https://agentmods.dev/commands/fatihkan/badi/retro"><img src="https://agentmods.dev/badge/commands/fatihkan/badi/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.1 | $0.00000 | $0.00571 |
| Opus 5 | $0.00000 | $0.00285 |
| Sonnet 5 | $0.00000 | $0.00114 |
| Haiku 4.5 | $0.00000 | $0.00057 |
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 — 124 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Sprint retrospective command. Analyzes the past period and identifies improvement areas.
Required Tools
- Read (daily notes, task board, memory)
- Bash (git statistics)
- Grep (pattern search)
- Write (report writing)
Procedure (4 Steps)
Step 1: Data Collection
Gather the data for the retrospective period:
Git Data:
- Commit count and distribution (by day)
- Changed file count
- Line add/delete statistics
- Branch and merge history
- Reverted commits
Task Data:
- Completed tasks and their durations
- Deferred or cancelled tasks
- Blocked tasks and their durations
- Scope changes
Note Data:
- Decisions in the daily notes
- Learnings and insights
- Problems and their solutions
- Handoff notes
Step 2: Pattern Analysis
Detect patterns in the collected data:
Productivity Patterns:
- Most productive days/hours
- Areas with the most commits
- Recurring bottlenecks
- Velocity changes (slowdowns, speedups)
Problem Patterns:
- Recurring errors
- Frequently blocked areas
- Scope-creep examples
- Communication gaps
Success Patterns:
- Approaches that ended well
- Effective solution strategies
- Successful collaboration examples
Step 3: Improvement Categorization
Classify the findings into 4 categories:
Keep Doing (Went Well):
- Practices that worked
- Successful approaches
- Habits worth keeping
Stop Doing (Went Badly):
- Time-wasting practices
- Ineffective approaches
- Recurring mistakes
Start Doing (New Experiments):
- Suggested new practices
- Tools worth trying
- Process improvements
Investigate (Unclear):
- Areas needing more data
- Hypotheses to test
- Topics awaiting a decision
Step 4: Structured Report
Output Format
=== BADI RETROSPECTIVE ===
Period: [start] - [end]
Total Days: [count]
## Metrics
- Commits: [count] (daily avg: [count])
- Completed Tasks: [count]
- Deferred: [count]
- Blocked: [count]
- Line Changes: +[added] / -[removed]
## Patterns
### Productivity
[detected patterns]
### Recurring Problems
[problem patterns]
### Successes
[success patterns]
## Action Plan
### Keep Doing
- [practice]
### Stop Doing
- [practice]
### Start Doing
- [new practice]
### Investigate
- [topic]
## Sprint Note
[overall assessment and a motivational note]
## Next Sprint Goals
1. [goal]
2. [goal]
3. [goal]
==========================
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 · 124 lines · 0 tokens per session scan A 908ae9c9d761
retro is a command published in the GitHub repository fatihkan/badi (7 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 571 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-06.
Other commands, from other repositories
plan-start
5-phase planning command: PRD analysis, design review, technical decisions, dynamic research team, metrics. Produces a complete implementation plan + ADRs before any code is written.
plan-ceo-review
Strategic product gate — challenge the brief, find the 10-star product hiding inside the request, before writing any code.
routines-discover
Analyzes the current project to surface high-value Routines use cases across the three trigger types (schedule, API, GitHub events). Usage: /routines-discover.
check-cache-bugs
Audit Claude Code setup for cache bugs (CC#40524) — sentinel, --resume/--continue, attribution header + ArkNill B3/B4/B5.
methodology-advisor
Analyzes your codebase and asks 3 targeted questions to recommend the right AI-assisted development methodology stack.
review-pr
Perform a comprehensive code review of a pull request.