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 awrshift/agent-memory-kit --skill close-sessiongit clone --depth 1 https://github.com/awrshift/agent-memory-kitWrote 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/awrshift/agent-memory-kit/close-session)<a href="https://agentmods.dev/skills/awrshift/agent-memory-kit/close-session"><img src="https://agentmods.dev/badge/skills/awrshift/agent-memory-kit/close-session/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/awrshift/agent-memory-kit/close-session"><img src="https://agentmods.dev/badge/skills/awrshift/agent-memory-kit/close-session.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00064 | $0.01082 |
| Opus 5.5 | $0.00026 | $0.00433 |
| Sonnet 5.5 | $0.00013 | $0.00216 |
| Haiku 4.5 | $0.00006 | $0.00108 |
Grade A, and why
close-session 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 8d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- close-session — 100% identical, 13 lines differ
How it starts
The opening of the file, as written. The whole thing — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/close-session — the end-of-session ritual
You close the session in four steps. Don't just dump — audit. Everything you write, you announce briefly; anything promoted to rules/concepts needs the user's verbal "yes" first.
Step 1 — Capture what's new
Scan this session for observations worth keeping. Append each to .claude/memory/MEMORY.md
as a ONE-LINE [YYYY-MM-DD]-prefixed entry. Short, scannable, no essays (long rationale
belongs in a concept article, step 2).
- File each line under a TOPIC heading of the patterns section (engineering, process,
infra, the domain…) — create the topic if none fits. Never open a heading named after the
session or the date (
### s66 (2026-09-25),## Session 65 wrap): the date lives in each line's prefix, the session narrative lives in the handoff (step 4). The SessionStart hook flags such headings. - Don't capture what the always-loaded layer already says (
CLAUDE.md, rules withoutpaths:) or a number whose source of truth lives elsewhere (a price table, a config) — point at the source instead of copying the value.
Step 2 — Audit & promote (the valuable part)
Read the date-tagged entries in MEMORY.md. Look for repetition: did this pattern appear on 3+ different dates? Surface 2-4 candidates, be specific: "noticed [date], [date], [date] you said X — codify as a rule or a concept article?"
- User says yes → write
knowledge/concepts/<topic>.md(facts + rationale; frontmatter perknowledge/index.mdspec) or.claude/rules/<name>.md(mechanical always/never constraint; only for patterns stable 6+ months). Updateknowledge/index.md(one line per concept). - Promoted or long-absorbed entries get PRUNED from MEMORY.md — that's how it stays under its caps (180 lines / 32 KB / 3000 chars per line).
- Writing a fact into a second place?
reference/doc-governance.md— one SSOT per fact, and when a fact changes you grep its restatements in the same pass. A product or architecture decision goes to the ledger instead —projects/<name>/decisions-log.md, format inreference/decisions-log.md. A plan, a spec, a research finding or a QA record is NOT memory: it belongs in that project's folder, per the map in itsREADME.md.
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.
- 8d ago Changed 812e86d26b3b
- 21d ago Changed · +9 lines aa0cbf392ae5
- 27d ago Changed · +2 lines aabe86407651
- 1mo ago First seen · 56 lines · 64 tokens per session scan A b6555f756a66
close-session is a skill published in the GitHub repository awrshift/agent-memory-kit (34 stars, last pushed 9d ago), licensed MIT. It adds 64 tokens to every session and 1,082 once invoked, about $0.0003 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
aictx
Use this skill when working in a repository that uses AICTX for repo-local operational continuity. Prefer AICTX MCP tools when available, fall back to CLI commands, resume before substantial work, and finalize factual continuity after work.
kayba-ace
This skill ships learnfromtraces.py, a script that reads OpenClaw session transcripts, feeds them through the ACE learning pipeline, and writes an updated skillbook to disk.
alive:save
The human wants to checkpoint. Or: the stash has grown heavy — 5+ items, 30+ minutes, a natural pause in the work. The squirrel doesn't decide when to save. It surfaces the need and lets the human pull the trigger. Runs the full save protocol: confirms stash, writes log, updates state, generates projections…
nav-compact
Clear conversation context while preserving knowledge via context marker. Use when user says "clear context", "start fresh", "done with this task", or when approaching token limits.
alive:capture-context
Use when external content arrives in the session — emails, transcripts, screenshots, documents, files, or in-session research worth keeping. Also use when there's nothing obvious to capture — the skill checks 03Inbox/ for unrouted files and enters inbox scan mode. Stores raw content, routes to bundles, extracts tasks…
alive:load-context
The human mentions a walnut to work on, asks about a specific venture/experiment/project, or wants to check status — not just explicit 'load X'. Load the brief pack (3 files), resolve the people involved, check the active bundle — then surface one observation and ask what to work on. Context loads in tiers: walnut and…