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 markmhendrickson/neotoma --skill close-sessiongit clone --depth 1 https://github.com/markmhendrickson/neotomaWrote 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/markmhendrickson/neotoma/close-session)<a href="https://agentmods.dev/skills/markmhendrickson/neotoma/close-session"><img src="https://agentmods.dev/badge/skills/markmhendrickson/neotoma/close-session.svg" alt="Measured on agentmods" 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.00066 | $0.00868 |
| Opus 5 | $0.00033 | $0.00434 |
| Sonnet 5 | $0.00013 | $0.00174 |
| Haiku 4.5 | $0.00007 | $0.00087 |
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 4d 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.
How it starts
The opening of the file, as written. The whole thing — 83 lines — stays where its author put it; the contents beside it link to each section on GitHub.
close-session
Specification status: This file is a specification, not a runnable skill. The core_workflows bundle is defined in m1 of the Bundles Strategy (plan ent_089da2ecebc3bd804d63dcf2); the runtime path that installs and auto-loads these skills lands in m2 alongside plan ent_b5a51d1395d206e10945b6b1 (Resolve #205). Until m2, treat this file as the locked spec the implementation MUST match.
Adapted in structure from the reference implementation in lemon-skills-share (https://github.com/Lemonbrand/lemon-skills-share). The interaction and session_close entity types are added by the core_workflows bundle to the core shared schemas at m2.
Purpose
End every session with a deterministic write-out. Nothing learned in-session should depend on the agent's working memory after termination. Every decision, every outbound message, every follow-up MUST land in the state layer or in a human-readable ledger.
When to use
- At the end of every working session.
- When the user says "wrap up", "we're done", "close out", or "save and exit".
- Before any planned context reset.
Required entity types
task, observation, interaction, session_close. The first two come from the default-install core bundle; the latter two are contributed by core_workflows to the shared schemas.
Process
Step 1: Archive locally
Snapshot the session transcript and any work-in-progress artifacts to the agent's local archive location. This is the safety net for everything downstream.
Step 2: Pull daily activity
Aggregate the entities touched this session (from start-session cache plus in-session writes).
Step 3: Store session_close entity
Write a session_close entity with:
- A summary of no more than 8 bullets.
- Each bullet no more than 240 characters.
- Links to the entity IDs touched.
- A timestamp.
Step 4: Write entity observations
For every entity whose state materially changed this session, write a new observation row capturing the change and its source.
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.
- 4d ago First seen · 83 lines · 66 tokens per session scan A 0d71ef6185b5
close-session is a skill published in the GitHub repository markmhendrickson/neotoma (31 stars, last pushed today), licensed MIT. It adds 66 tokens to every session and 868 once invoked, about $0.0003 per session on Opus 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-09-03.
Other skills, from other repositories
mk:wiki
Capture, gate, query, and render long-term project knowledge through the gated mewkit wiki subsystem. Use to create a wiki, propose/approve candidates (scanner-gated), hand off a skill's terminal artifact as a scanned candidate, recall context, search the FTS index, or list pages. Agents may only PROPOSE candidates…
mempalace-task
Create, hand off, claim, execute, and close agent tasks through the MemPalace logstream. Use when the user wants to delegate work, prepare a ready-to-paste task for another agent, receive a MemPalace task id, or explicitly launch a supported headless agent in controlled mode.
commonly
You are a member of a Commonly workspace — a shared space where humans and AI agents from any origin collaborate in pods (chat rooms with memory). Use this whenever you are connected to Commonly via the commonly MCP tools: to read what's happening, post, remember things across sessions, react, DM other agents, and…
bernstein-plan
Create and manage multi-step execution plans in Bernstein. Plans decompose complex goals into stages with dependencies. Use when the user wants to plan a complex feature, break down a large task, or review an execution plan before agents start working.
state
Use when the user says 'update state', 'project state', 'where was I', or at session start to load current context.
okf-pro
Operating rules for the .okf/ knowledge bundle — filing new concepts, the board, the journal, the daily snapshot, closing work, source attribution, and the generated/verified attestation policy. Use before reading from or writing anything into .okf/.