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 commands/isaacsight/kernel/retrogit clone --depth 1 https://github.com/isaacsight/kernelWrote 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/isaacsight/kernel/retro)<a href="https://agentmods.dev/commands/isaacsight/kernel/retro"><img src="https://agentmods.dev/badge/commands/isaacsight/kernel/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.00440 |
| Opus 5 | $0.00000 | $0.00220 |
| Sonnet 5 | $0.00000 | $0.00088 |
| Haiku 4.5 | $0.00000 | $0.00044 |
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 2d 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 team retrospective. Agents review accumulated knowledge, prune stale entries, and identify tool gaps.
Protocol
1. Load All Memories
Read all agent memory files:
- Call
agent_memory_readfor each:qa,designer,performance,security,devops,product - Also read
shared-knowledgeandtool-effectiveness
2. Analyze Patterns
For each agent's memory, identify:
- Recurring issues — Problems that keep appearing (indicate systemic issues)
- Stale entries — Findings that are no longer relevant (fixed issues, outdated metrics)
- Wins — Successful patterns worth reinforcing
- Gaps — Things agents needed but couldn't do
3. Prune Stale Entries
For each stale entry found:
- Note what was stale and why
- Suggest removal (but do NOT auto-delete — list for human review)
4. Identify Tool Gaps
Review tool-effectiveness.md for:
- Tools with high failure rates
- Agents that frequently work around missing capabilities
- Propose new tools via
create_toolif clear gaps emerge
5. Update Shared Knowledge
Call agent_memory_write for shared-knowledge with:
- Key cross-cutting patterns discovered
- Updated architecture decisions
- Resolved coordination notes
6. Generate Retro Report
# Team Retrospective — [date]
## What's Working
[patterns and tools that consistently deliver value]
## Recurring Issues
[problems that keep appearing — need systemic fixes]
## Stale Entries (suggest pruning)
[entries that are no longer relevant, grouped by agent]
## Tool Effectiveness
| Tool | Uses | Success Rate | Notes |
|------|------|-------------|-------|
## Tool Gaps
[capabilities agents need but don't have]
## Proposed Tools
[new tools created via create_tool, if any]
## Action Items
1. [highest priority systemic fix]
2. [next priority]
...
7. Notify
Call kernel_notify on discord with retro summary.
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.
- 2d ago First seen · 72 lines · 0 tokens per session scan A 15be7a9e017f
retro is a command published in the GitHub repository isaacsight/kernel (16 stars, last pushed 7d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 440 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-03.
Other commands, from other repositories
guard
Show the latest covguard run, spend against the cap, outcome, and receipt.
AGENTS
Command "AGENTS" from binary16labs/prime-silo, covering agents, purpose, documentation hierarchy, how to document command child docs and contract.
agentlas-cloud
Staff a task only from the signed-in owner's Agent Cloud agents.
memory-ingest
You capture valuable analysis, discoveries, or decisions from the current conversation and file them into the MEMORY.md wiki AND MemPalace verbatim store. This is the "query results file back" pattern: good answers shouldn't disappear into chat history.
explain
You are helping a non-technical product manager understand code or concepts.
nl-branch
自然语言分支选择（L1 优先） — 演示 keywordAliases 关键词匹配触发分支，用户只需说"快速"或"深入".