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 skills add Heapy/kortex --skill amnesiagit clone --depth 1 https://github.com/Heapy/kortexWrote 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/skills/heapy/kortex/amnesia)<a href="https://agentmods.dev/skills/heapy/kortex/amnesia"><img src="https://agentmods.dev/badge/skills/heapy/kortex/amnesia/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/skills/heapy/kortex/amnesia"><img src="https://agentmods.dev/badge/skills/heapy/kortex/amnesia.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.00090 | $0.00456 |
| Opus 5.5 | $0.00036 | $0.00182 |
| Sonnet 5.5 | $0.00018 | $0.00091 |
| Haiku 4.5 | $0.00009 | $0.00046 |
Grade A, and why
amnesia 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 27d 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
Amnesia
Overview
Reorient the user after they stepped away. Report what the session is, where it left off, and what changed while they were gone.
Answer from the conversation already in context. Do not re-run builds, re-read files, or start new work to produce this recap.
Output
Report these four sections, in order.
Session started
When this session began. Use timestamps available in the conversation context. If no timestamp is available, say so plainly instead of guessing — an approximation stated as fact is worse than "unknown".
Last user message
When the user last wrote, and the verbatim text of that message — the one before this request, not this request itself. Quote it; do not paraphrase. If it was long, quote the first few lines and mark it as truncated.
Since then
What happened after that message: files created or modified, commands run and their outcome, conclusions reached, questions asked and still unanswered. Include failures and abandoned attempts — those are the part a returning user is most likely to have missed.
Also worth knowing
Significant changes from earlier in the session that are still relevant: decisions made, approaches reversed, work left unfinished, anything agreed to but not yet done. Skip this section entirely if the session holds nothing beyond what the previous section already covered.
Rules
- Be brief. This is a status readout, not a transcript.
- Never invent timestamps, file names, or outcomes. Unknown is an acceptable answer.
- Distinguish what was done from what was only proposed.
- If the session has no prior user message, say that this is the first turn and stop.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 27d ago Changed · +1 lines a3b992410966
- 1mo ago First seen · 52 lines · 90 tokens per session scan A 0c37cd66237d
amnesia is a skill published in the GitHub repository Heapy/kortex (7 stars, last pushed yesterday), licensed Apache-2.0. It adds 90 tokens to every session and 456 once invoked, about $0.0004 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 skills, from other repositories
codex-history-recovery
A recovery tool for Codex Desktop conversation history when chats become hidden after changing accounts, API keys, providers, or models.
learning-memory
Use when capturing or restoring a learner's persistent profile to personalize teaching across sessions.
codex-session-history
List and inspect local Codex session history by reading /.codex/sessionindex.jsonl, /.codex/sessions/, and /.codex/archivedsessions/. Default to unarchived sessions in /.codex/sessions/. Use when users ask what Codex sessions exist, want each session's id or title, need to know which project or workspace a session…
principle-guard-the-context-window
Apply when context is filling up: large outputs, long files, repeated reads, fan-out planning. Route bulk to subagents; keep summaries in the main thread, not raw payloads.
promote-memory
Review candidate learnings in Claude Code's native auto memory (/.claude/projects/ /memory/, machine-local) and run them through a five-critic council in parallel: generality, staleness, redundancy, evidence, format. Majority vote (3+ of 5) promotes the entry to MEMORY.md. Use when user says "promote memory", "review…
compress-session
Distill the current conversation into a structured note (decisions made, open questions, file pointers with line numbers, next 1–3 actions) and save to qualityreports/sessionlogs/ before auto-compression. Differs from /checkpoint (explicit stop-point snapshot) and from auto-compaction (which truncates rather than…