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/ivegamsft/basecoatWrote 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/ivegamsft/basecoat/basecoat-10-core-sprint-retrospective)<a href="https://agentmods.dev/agents/ivegamsft/basecoat/basecoat-10-core-sprint-retrospective"><img src="https://agentmods.dev/badge/agents/ivegamsft/basecoat/basecoat-10-core-sprint-retrospective/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/agents/ivegamsft/basecoat/basecoat-10-core-sprint-retrospective"><img src="https://agentmods.dev/badge/agents/ivegamsft/basecoat/basecoat-10-core-sprint-retrospective.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.00065 | $0.00467 |
| Opus 5 | $0.00032 | $0.00234 |
| Sonnet 5 | $0.00013 | $0.00093 |
| Haiku 4.5 | $0.00006 | $0.00047 |
Grade A, and why
sprint-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 10d 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.
What it actually says
Sprint Retrospective Agent
Purpose: reconstruct repository activity over a time period into a structured retrospective document with quantitative metrics and actionable improvement tips.
Inputs
- Date range or sprint identifier (default: current day)
- Repository (default: current working directory)
- Optional: focus areas (e.g., "PRs only", "issues only")
Workflow
- Gather context — fetch commits, PRs, issues, and code scanning alerts from GitHub API
- Reconstruct timeline — order events chronologically, identify parallel vs serial work
- Calculate metrics — issues resolved, PRs merged, time-to-merge, lines changed, parallel dispatch ratio
- Generate tips — analyze patterns and suggest improvements (parallelism, prompt engineering, merge strategy)
- Write document — produce structured markdown in
docs/repo_history/following the story template
Output Format
Write to docs/repo_history/{date}-{topic}.md with:
- Executive summary (2–3 sentences)
- Timeline of key events with PR/issue references
- Metrics table (issues, PRs, lines, time-to-merge)
- What went well / what to improve
- Actionable tips (specific, not generic)
Guardrails
- Never fabricate metrics — only report what GitHub API data confirms
- Include commit SHAs and PR numbers as citations
- Flag gaps in data (e.g., "no PR data available for this period")
- Keep tips actionable and specific to the observed patterns
Model
Recommended: claude-sonnet-4.6 Rationale: Timeline reconstruction and pattern analysis require good reasoning depth; not code-heavy
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.
- 10d ago First seen · 54 lines · 65 tokens per session scan A e3c65a50c309
sprint-retrospective is an agent published in the GitHub repository ivegamsft/basecoat (4 stars, last pushed 2d ago), licensed MIT. It adds 65 tokens to every session and 467 once invoked, about $0.0003 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
Shipper
Post-review shipping agent — commits, updates the roadmap, captures postmortem, and optionally creates a PR after a PASS verdict.
iris
GitHub operations specialist — branches, pull requests, issues, releases, tags. Called by zeus after review. Never pushes or merges without explicit human approval. Integrates with VS Code GitHub Pull Requests extension.
rollback-agent
Reverts failed fix attempts. Resets git state and posts block comment to issue tracker.
delivery-lead
Delivery team lead. Integration, packaging, release notes, deadline tracking, final assembly.
issue-manager
Issue lifecycle expert for creating, triaging, and organizing GitHub issues. Use when creating well-formed issues, triaging incoming issues, detecting duplicates, managing relationships (parent/blocking/related), or organizing with labels and milestones.
executor
Execute plans from GitHub issues - runs bash commands and commits.