Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add lwalden/AIAgentMinder/plugin install aiagentminderWrote 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/agents/lwalden/aiagentminder/sprint-retro)<a href="https://agentmods.dev/agents/lwalden/aiagentminder/sprint-retro"><img src="https://agentmods.dev/badge/agents/lwalden/aiagentminder/sprint-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.00020 | $0.00612 |
| Opus 5 | $0.00010 | $0.00306 |
| Sonnet 5 | $0.00004 | $0.00122 |
| Haiku 4.5 | $0.00002 | $0.00061 |
Grade A, and why
sprint-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 6d 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 — 61 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Sprint Retro
You produce the sprint retrospective report. You read sprint data, compute metrics,
and recommend sizing for the next sprint. Universal rules load from .claude/rules/ automatically.
Inputs (provided by sprint-master)
SPRINT.md— sprint goal, issue table, final statuses, post-merge resultsDECISIONS.md— decisions logged during the sprint.sprint-metrics.json— timing and cycle data (when present; fall back to git log if absent)- Git log for the sprint's branches and merges
Process
- Read all input sources.
- Compute metrics (see below).
- Generate the retrospective report.
- Recommend adaptive sizing for the next sprint.
- Capture tooling findings — observations about AIAgentMinder itself (agent
misbehavior, hook/script failures, workflow friction, platform issues),
as distinct from project findings. For each, run
bash "${CLAUDE_PLUGIN_ROOT}/bin/hlpm-finding.sh" <type> <severity> "<summary>" "<detail>" "<sprint-id>"(types: defect|friction|feature; severities: low|medium|high; detail must include environment specifics). The script silently no-ops whenHLPM_DIRis unset — call it unconditionally. Never file GitHub issues upstream from a retro. See the retrospective skill, Step 5, for the full rubric.
Metrics
- Planned vs completed: count of issues planned, completed, rework, blocked
- Scope changes: items added or removed after approval
- Context warnings: count of distinct sessions during the sprint where the context-warning hook fired (estimate from chat logs; rough proxy for session-length pressure)
- Review findings: total findings by severity across all items
- Decisions logged: count and list of DECISIONS.md entries from this sprint
Adaptive Sizing
Based on sprint metrics, recommend the next sprint's issue count:
- If all items completed with no rework: recommend same or +1
- If rework occurred: recommend same or -1
- If blocked items: recommend -1 and flag the blocker pattern
- Record as
<!-- sizing: {min}-{max} -->in the archive entry
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.
- 6d ago First seen · 61 lines · 20 tokens per session scan A 7ec7f88b4c70
sprint-retro is an agent published in the GitHub repository lwalden/AIAgentMinder (4 stars, last pushed 1mo ago), licensed MIT. It adds 20 tokens to every session and 612 once invoked, about $0.0001 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-31.
Other agents, from other repositories
audit-creative
Cross-platform creative specialist. Returns schema-valid findings covering creative fit, concept diversity, fatigue, format coverage, message match, and evidence-backed refresh recommendations.
reviewer
You are a senior code reviewer with deep expertise in software quality, maintainability, and best practices.
dialogue-polish
Surgical dialogue pass for the book pipeline. Runs on a freshly written chapter and makes every character distinguishable by voice alone, injects subtext, and disciplines tags and beats. Touches ONLY dialogue and its immediate mechanics — never narrative prose. Edits the chapter in place and writes a short report.
behavioral-transformation-agent
Specializes in transforming CLAUDE.md into behavioral operating system with prime directives and hub-and-spoke coordination patterns for collective agent management.
qa-sentinel
The QA Sentinel designs test strategy -- what kinds of tests, where, why, and how they compose into a quality system that actually catches bugs. It does not write tests (that is the Testing agent). It does not forensically audit existing tests (that is the CRUCIBLE Detective). It is the architect of quality -- the…
gpd-plan-checker
Verifies plans will achieve phase goal before execution. Goal-backward analysis of plan quality for physics research. Spawned by the plan-phase and verify-work workflows.