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 ils15/pantheon-legacy --skill handoffgit clone --depth 1 https://github.com/ils15/pantheon-legacyWrote 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/ils15/pantheon-legacy/handoff)<a href="https://agentmods.dev/skills/ils15/pantheon-legacy/handoff"><img src="https://agentmods.dev/badge/skills/ils15/pantheon-legacy/handoff/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/ils15/pantheon-legacy/handoff"><img src="https://agentmods.dev/badge/skills/ils15/pantheon-legacy/handoff.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.00018 | $0.01111 |
| Opus 5 | $0.00009 | $0.00556 |
| Sonnet 5 | $0.00004 | $0.00222 |
| Haiku 4.5 | $0.00002 | $0.00111 |
Grade A, and why
handoff 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.
How it starts
The opening of the file, as written. The whole thing — 167 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Handoff — Session Continuation Summary
Use this skill to generate a structured handoff summary when transitioning work to a new session.
Policy-safe storage: keep handoffs in /memories/session/ during the conversation. Do not create ad-hoc .md files in the repository root.
When to Use
- Session is ending but work is incomplete
- Computer crash or logout mid-feature
- Switching to a different machine
- User wants to start fresh but continue the same work
- Context window is getting full and a fresh session would help
Handoff Format
# Handoff: <Feature Name>
## Current Status
- Wave N completed (<description>)
- Wave N+1 pending (<description>)
- Current task: <what was being worked on>
## What Was Completed
- <file/path> — <what was implemented>
- <file/path> — <what was implemented>
- <file/path> — <what was implemented>
## Remaining Work
- <remaining task 1>
- <remaining task 2>
- <remaining task 3>
## Key Decisions
- <decision 1> (rationale)
- <decision 2> (rationale)
## Learnings (from wisdom accumulation)
- <convention 1>
- <gotcha 1>
- <failure to avoid 1>
## Relevant Files
- <path/to/file1>
- <path/to/file2>
- <path/to/file3>
## Tasks Status (if using Task System)
- T-001 [completed] <subject>
- T-002 [completed] <subject>
- T-003 [in_progress] <subject>
- T-004 [pending] <subject>
## Next Steps
1. <immediate next action>
2. <following action>
3. <eventual action>
How to Persist Handoff (Policy-Compliant)
When user runs /handoff:
1. Mnemosyne reads current session state
2. Mnemosyne reads /memories/session/* (if relevant)
3. Mnemosyne generates handoff summary
4. Mnemosyne saves to /memories/session/handoff-<timestamp>.md
5. Mnemosyne outputs the summary in chat
6. At sprint close, promote only durable context to .pantheon/memory-bank via explicit @mnemosyne action
How New Session Uses Handoff
When starting a new session:
1. User pastes handoff document (or references file path)
2. New session reads handoff
3. Agent resumes from "Next Steps"
4. Tasks continue from last known state
5. Learnings are re-injected
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 · 167 lines · 18 tokens per session scan A 4b9dffdc6c70
handoff is a skill published in the GitHub repository ils15/pantheon-legacy (10 stars, last pushed 6d ago), licensed MIT. It adds 18 tokens to every session and 1,111 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
media-ingest
Ingest video, audio, PDF, book, screenshot, and GitHub repo content into the brain. Multi-format handling with entity extraction and backlink propagation. Covers video-ingest, youtube-ingest, and book-ingest subtypes.
mem0-oss-to-platform
Plan and then execute a migration of a project from the mem0 open-source / self-hosted SDK (the local Memory class) to the mem0 Platform / hosted / managed SDK (the MemoryClient class). Use this whenever a developer wants to move, switch, or migrate their mem0 usage off OSS/self-hosted to the hosted API — e.g.…
Cortex
Operate Cortex, the LifeOS memory system — the typed Knowledge Archive (People, Companies, Ideas, Research with typed related: links) plus recall of prior work sessions, ISAs, and conversations. Search, add, harvest, develop, ingest, distill, graph-navigate, recall. USE WHEN cortex, knowledge, knowledge base, search…
memory
Use when the user asks to remember, recall, forget, update, search, or inspect durable OpenSquilla memory, including profile facts in USER.md and long-term notes in MEMORY.md or memory//.md.
ha-data-stores
Map of Hope Agent's local data stores and safe read-only query workflow. Use when the user asks where Hope Agent stores data, wants to inspect sessions/messages/memory/logs/background jobs/knowledge indexes/settings, asks the model to query local app data, or debugging requires checking persisted state. Trigger…
establishing-project-context
Use when the user asks to establish shared project language, or project work exposes a conflicting, renamed, or deprecated domain term that needs active semantic modeling. Routine small tasks stay on the fast path.