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/jasonhnd/life_os/retrospectivegit clone --depth 1 https://github.com/jasonhnd/life_OSWrote 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/jasonhnd/life_os/retrospective)<a href="https://agentmods.dev/agents/jasonhnd/life_os/retrospective"><img src="https://agentmods.dev/badge/agents/jasonhnd/life_os/retrospective.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.00000 | $0.00234 |
| Opus 5 | $0.00000 | $0.00117 |
| Sonnet 5 | $0.00000 | $0.00047 |
| Haiku 4.5 | $0.00000 | $0.00023 |
Grade A, and why
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 5d 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
Retrospective
Useful when
The user wants to understand progress, setbacks, decisions, or recurring patterns across a defined period or body of work.
Skip when
No review was requested, the period is undefined, or there is too little evidence to distinguish a pattern from one event.
Suggested inputs
- selected time period, project, or records;
- intended outcome and relevant decisions;
- observed results, setbacks, and changes;
- the user's desired follow-up.
Useful questions
- What changed relative to the intended outcome?
- Which evidence supports a repeated pattern?
- What worked and should be retained?
- What is the smallest useful adjustment?
Possible output
A period summary, lessons, pattern-and-evidence table, or focused next actions.
Safety
Do not auto-run at session start, pull remote data, or persist the result unless the request includes those actions. Avoid turning limited evidence into a personal diagnosis.
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.
- 5d ago First seen · 44 lines · 0 tokens per session scan A ea318495ebda
retrospective is an agent published in the GitHub repository jasonhnd/life_OS (5 stars, last pushed 28d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 234 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-08-31.
Other agents, from other repositories
council-karpathy
Council member. Use standalone for neural network intuition & empirical ML analysis, or via /council for multi-perspective deliberation.
council-taleb
Council member. Use standalone for antifragility & tail risk analysis, or via /council for multi-perspective deliberation.
council-aurelius
Council member. Use standalone for resilience & moral clarity analysis, or via /council for multi-perspective deliberation.
council-lao-tzu
Council member. Use standalone for emergence & non-intervention analysis, or via /council for multi-perspective deliberation.
council-meadows
Council member. Use standalone for systems thinking & feedback loop analysis, or via /council for multi-perspective deliberation.
council-musashi
Council member. Use standalone for strategic timing & situational awareness analysis, or via /council for multi-perspective deliberation.