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 albatrossflyon-coder/claude-token-operator-kit --skill save-sessiongit clone --depth 1 https://github.com/albatrossflyon-coder/claude-token-operator-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/albatrossflyon-coder/claude-token-operator-kit/save-session)<a href="https://agentmods.dev/skills/albatrossflyon-coder/claude-token-operator-kit/save-session"><img src="https://agentmods.dev/badge/skills/albatrossflyon-coder/claude-token-operator-kit/save-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/albatrossflyon-coder/claude-token-operator-kit/save-session"><img src="https://agentmods.dev/badge/skills/albatrossflyon-coder/claude-token-operator-kit/save-session.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.00028 | $0.02459 |
| Opus 5.5 | $0.00011 | $0.00984 |
| Sonnet 5.5 | $0.00006 | $0.00492 |
| Haiku 4.5 | $0.00003 | $0.00246 |
Grade A, and why
save-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 1mo 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 — 297 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Save Session Command
Capture everything that happened in this session: what was built, what worked, what failed, what's left: and write it to a dated file so the next session can pick up exactly where this one left off.
When to Use
- End of a work session before closing Claude Code
- Before hitting context limits (run this first, then start a fresh session)
- After solving a complex problem you want to remember
- Any time you need to hand off context to a future session
Process
Step 1: Gather context
Before writing the file, collect:
- Read all files modified during this session (use git diff or recall from conversation)
- Review what was discussed, attempted, and decided
- Note any errors encountered and how they were resolved (or not)
- Check current test/build status if relevant
Step 1b: Verify pending items before listing them
This step is mandatory. Before writing any item to "Pending", "Next Steps", or "What Has NOT Been Tried Yet", verify it is actually undone. Never carry over an item based on memory alone.
For each candidate pending item, run the appropriate check:
| Item type | Verification command |
|---|---|
| Tool install | tool --version or tool init --show |
| Hook/config change | Read the relevant settings.json or CLAUDE.md |
| Repo push | git log --oneline -5 in that repo |
| File edit | Read the target file and confirm the change isn't there |
| Script/scheduler | Check Task Scheduler or cron with the relevant list command |
Verdict rules:
- If verification confirms it IS done → mark ✅ DONE, do not list as pending
- If verification fails or item genuinely not done → list as pending with the exact verification command so the next session can re-check in 10 seconds instead of re-discovering over 10 minutes
- If the item cannot be verified without user input → note it explicitly:
[NEEDS CHRIS TO VERIFY: <what to check>]
The rule: If something was on last session's pending list and you haven't verified it's still undone, do not carry it forward. Carrying over ghost tasks wastes entire sessions re-discovering already-done work.
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.
- 1mo ago First seen · 297 lines · 28 tokens per session scan A fd53eba4f15f
save-session is a skill published in the GitHub repository albatrossflyon-coder/claude-token-operator-kit (5 stars, last pushed 2mo ago), licensed MIT. It adds 28 tokens to every session and 2,459 once invoked, about $0.0001 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
knowledge-ingest
Ingest documents, articles, conversations, or supplied text into Knowledge with retained originals, sourced claims, entity updates, timelines, and cross-links; also learn durable lessons from a set of conversations, transcripts, or past sessions (/learn), including the Learn from conversations and Learn from Memory…
forget
Remove a personal fact, preference, relationship detail, topic, or prior event from Muse's active memory and stop existing copies or automations from bringing it back. Use for explicit requests such as 'forget that', 'don't remember this about me', or 'remove that from your memory'. Do not use when 'forget it' merely…
mem0-oss-to-platform
Plan, then execute, a migration of a project from the mem0 open-source / self-hosted SDK (local Memory class) to the mem0 Platform / hosted SDK (MemoryClient). TRIGGER when: the developer wants to move, switch, or migrate mem0 off OSS/self-hosted to the hosted API, e.g. "migrate my mem0 setup to the platform", "switch…
Cortex
LifeOS memory, prior-session recall, and learning capture. USE WHEN capture this learning, document this learning, what did we learn recently, recent learnings, cortex, knowledge, knowledge base, search knowledge, what do we know about, archive, harvest, knowledge status, develop note, add to knowledge, add a people…
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…