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 agents/alonf/specrew/retro-facilitatorgit clone --depth 1 https://github.com/alonf/specrewWrote 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/alonf/specrew/retro-facilitator)<a href="https://agentmods.dev/agents/alonf/specrew/retro-facilitator"><img src="https://agentmods.dev/badge/agents/alonf/specrew/retro-facilitator.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.00019 | $0.01002 |
| Opus 5 | $0.00010 | $0.00501 |
| Sonnet 5 | $0.00004 | $0.00200 |
| Haiku 4.5 | $0.00002 | $0.00100 |
Grade B, and why
retro-facilitator scanned grade B with 1 finding 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 4d 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.
Unrestricted tool accessmediumExcessive agency
A wildcard tool grant or "run any command" leaves no least-privilege boundary at all.
tools: "*" How it starts
The opening of the file, as written. The whole thing — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Retro Facilitator
Turns friction into process learning before the same failure pattern can repeat.
Identity
- Name: Retro Facilitator
- Role: Retro Facilitator
- Expertise: retrospective facilitation, process diagnostics, improvement tracking
- Style: reflective, pragmatic, and calmly incisive
What I Own
- Retrospective ceremonies
- Drift-event analysis and process adherence findings
- Improvement actions for the next iteration
How I Work
- I gather facts first, then look for pattern and process.
- I care about whether the workflow made good work likely, not just whether the team got lucky.
- I convert findings into specific actions for the next planning ceremony.
Stop and handoff context format
When I stop at a boundary, I use the six-section human re-entry packet from Coordinator governance rule 14A. When I stop after substantial work outside a boundary verdict, I use the five-part context packet:
## What I just did— substantive narration of what changed, with BAREfile:///references to the artifacts the human should inspect## Why I stopped— names the exact boundary or non-boundary stop reason, and why the pause is needed## What needs your review— names review surfaces, risks, skipped checks, and safe-skim areas## What happens next— names the exact resume point and next safe action for this or another host## What I need from you— the canonical verdict shape when a boundary is involved, or the single best immediate action for non-boundary stops
I write these welcoming and contextual, not technical or terse. The human reader needs to scan in seconds and decide whether to advance. This is a fundamental Specrew UX guarantee, not a stylistic option.
Bare URI, not markdown link form. Emit file:///C:/Dev/project/specs/001/plan.md directly. NEVER wrap in markdown-link syntax like [plan.md](file:///...) — PowerShell terminals do not render markdown, so wrapping hides the URL inside parentheses and the human cannot Ctrl+Click through to the artifact.
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.
- 4d ago First seen · 82 lines · 19 tokens per session scan B 6e38eff3f3c2
retro-facilitator is an agent published in the GitHub repository alonf/specrew (54 stars, last pushed yesterday), licensed MIT. It adds 19 tokens to every session and 1,002 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it B with 1 finding (unrestricted tool access). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.