Getting it into your agent
There is no command for this one: it runs only inside a plugin, and the catalogue could not identify which plugin ships it. The source is linked below.
Wrote 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/gsaranti/pantheon/metis-session-end)<a href="https://agentmods.dev/skills/gsaranti/pantheon/metis-session-end"><img src="https://agentmods.dev/badge/skills/gsaranti/pantheon/metis-session-end/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/gsaranti/pantheon/metis-session-end"><img src="https://agentmods.dev/badge/skills/gsaranti/pantheon/metis-session-end.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.00018 | $0.00525 |
| Opus 5 | $0.00009 | $0.00262 |
| Sonnet 5 | $0.00004 | $0.00105 |
| Haiku 4.5 | $0.00002 | $0.00052 |
Grade A, and why
metis-session-end 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 9d 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
/metis-session-end
Close out the session: rewrite .metis/CURRENT.md.
Preconditions
.metis/ must exist. If it does not, stop and point at /metis-init.
Load
- The current
.metis/CURRENT.md. .metis/BUILD.md, when an item was completed this session — so the finished item can move to Built and the active-task pointer can advance.Readit before theEdit.- The session's in-flight state from conversation context — what just happened, what was decided, what is queued, any plan or scope report mid-flow, and any review verdicts.
Do not load
- Other
.metis/artifacts (SYNTHESIS.md,INDEX.md,CONTRADICTIONS.md,QUESTIONS.md,RESOLVED.md). The handoff is about session state, not project state. docs/.
Read first
references/session-handoff.md — read before writing the handoff.
Write scope
.metis/CURRENT.md— full rewrite. The handoff is the cumulative summary of session state, not an append log..metis/BUILD.md— only when an item is fully complete (its last task review-approved) this session: a surgicalEditmoving that item from To build to Built. An item still in progress stays put; its progress is recorded inCURRENT.mdinstead. Nothing else in the file changes.
Do not write to
- Other
.metis/files. docs/..claude/.
Invocation prompt
Trailing prompt: see ${CLAUDE_PLUGIN_ROOT}/references/command-prompts.md.
Return
- Handoff summary — the blocks of the new
CURRENT.md, rendered inline. - Backlog updates — any item moved to Built and the new active item; for an item still in progress, the next step recorded in Current state. "No change" if nothing advanced.
- Pending decisions — any architectural choice made this session that should be remembered next time but wasn't captured (in the docs, in code, or in a commit message). Surfaced as a flag for the user.
- Next step — typically the session ends here.
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.
- 9d ago First seen · 51 lines · 18 tokens per session scan A ec7244afa3ff
metis-session-end is a skill published in the GitHub repository gsaranti/pantheon (3 stars, last pushed 17d ago), licensed MIT. It adds 18 tokens to every session and 525 once invoked, about $0.0001 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-08-31.
Other skills, from other repositories
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…
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:session-history
Revive sessions (quick or heavy), browse, and search — 'what happened recently?', 'find the session where we discussed X', 'revive yesterday's session'. For single-session recall and multi-session browsing. If the human needs to merge multiple sessions into one working context or detect conflicts between parallel…
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…
alive:mine-for-context
Deep context extraction from source material. Creates reference bundles, builds extraction plans, tracks what's been extracted, and discovers new targets — people, subjects, patterns, connections. The archaeologist that turns raw sources into structured knowledge. Can be invoked by alive:session-history for targeted…
alive:my-context-graph
Render an interactive map of your world. Generates the world index from all walnut and bundle frontmatter, then produces a force-directed graph showing connections between walnuts, people, bundles, and tags. Opens in the browser.