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/SarutobiSasuke8/agentops-templateWrote 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/sarutobisasuke8/agentops-template/retro)<a href="https://agentmods.dev/commands/sarutobisasuke8/agentops-template/retro"><img src="https://agentmods.dev/badge/commands/sarutobisasuke8/agentops-template/retro/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/commands/sarutobisasuke8/agentops-template/retro"><img src="https://agentmods.dev/badge/commands/sarutobisasuke8/agentops-template/retro.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.00012 | $0.00225 |
| Opus 5.5 | $0.00005 | $0.00090 |
| Sonnet 5.5 | $0.00002 | $0.00045 |
| Haiku 4.5 | $0.00001 | $0.00022 |
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 1mo 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
Run a lightweight end-of-session retrospective on the work done in this conversation.
Steps:
- Check
git diff HEADandgit statusto see what actually changed. - Review the conversation for decisions made, problems hit, and anything that felt awkward or slow.
Report in this format:
## What worked
- <approach, tool, or habit that helped>
## What slowed us down
- <friction point — unclear spec, repeated correction, missing context, etc.>
## AGENTS.md candidates
- <convention, rule, or preference worth codifying so future sessions don't repeat the same mistake or rediscover the same approach>
## Open questions
- <anything unresolved that should land in TODO.md or ROADMAP.md>
After the report, ask: "Want me to add any AGENTS.md candidates or open questions to the right file?"
Keep the retro honest and specific. Do not pad it. If the session was smooth, say so briefly and note only genuine candidates.
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.
- 1mo ago First seen · 30 lines · 12 tokens per session scan A cdf24f6542ca
retro is a command published in the GitHub repository SarutobiSasuke8/agentops-template (9 stars, last pushed 28d ago), licensed MIT. It adds 12 tokens to every session and 225 once invoked, about $0.0000 per session on Opus 5.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 commands, from other repositories
deps-audit
Audit project dependencies for vulnerabilities, outdated packages, license conflicts, and supply chain risks — then provide actionable remediation strategies.
lians-recall
Recall current (non-stale) facts from Lians memory, optionally as-of a past date.
migrate
Command "migrate" from chohra-med/expo_boilerplate, covering invocation, steps and rule.
react-native
Command "react-native" from getsentry/toolkit, covering xcode build step (react-native xcode) and important notes.
cost-tracker
Track session costs, understand token spend, and get optimization tips.
rev
Invoke Code Reviewer for code quality, security, requirements validation, and best practices review.