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 kriscard/Skills --skill save-sessiongit clone --depth 1 https://github.com/kriscard/SkillsWrote 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/kriscard/skills/save-session)<a href="https://agentmods.dev/skills/kriscard/skills/save-session"><img src="https://agentmods.dev/badge/skills/kriscard/skills/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/kriscard/skills/save-session"><img src="https://agentmods.dev/badge/skills/kriscard/skills/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.00031 | $0.00685 |
| Opus 5.5 | $0.00012 | $0.00274 |
| Sonnet 5.5 | $0.00006 | $0.00137 |
| Haiku 4.5 | $0.00003 | $0.00068 |
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 3d 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 — 80 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Save Session
Preserve what happened in this session so the user can resume or understand it later. This is a dated
record, not an Atomic Note and not a replacement for the issue tracker. Use create-note separately
when a lesson deserves reusable Knowledge.
1. Establish the evidence
Read ../vault/SKILL.md and the live AGENTS.md. Review the available conversation and its tool
results. Incorporate supplied context without treating a request or attempted action as a completed
result. If history was compacted or unavailable, state the coverage limit.
Collect outcomes, decisions and reasons, useful examples, changed files, verification results, and work deliberately deferred. Separate pre-existing changes from work performed in this session. Exclude credentials, secrets, and unnecessary personal or workplace data.
Completion: every claimed outcome has session evidence; failures and unverified work remain explicit.
2. Resolve the session note
Use the real local date, a short descriptive title, and the schema-defined session directory. Inspect any existing note with the same title/date. Ask before updating it; otherwise choose a distinct path. Never overwrite a previous session merely because it happened on the same day.
Read a live session template if one exists. Otherwise use this outline with the session metadata required by the schema:
# Session title
## Summary
What this session was about and how it ended.
## What was done
Verified actions and outcomes.
## Decisions
What was chosen, why, and relevant alternatives.
## Useful examples
Commands, code, or explanations worth keeping.
## Changed files
Paths and the purpose of each session change.
## Deferred work
Unfinished work, known limitations, and questions left open.
Omit sections without evidence. Account for every known session-changed file, grouping repetitive paths only when the complete file list remains available in a linked receipt. Include useful detail without dumping the transcript or raw tool output. Keep planned and completed work distinct.
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.
- 3d ago First seen · 80 lines · 31 tokens per session scan A 771d9199b0f0
save-session is a skill published in the GitHub repository kriscard/Skills (14 stars, last pushed 2d ago), licensed MIT. It adds 31 tokens to every session and 685 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-10-15.
Other skills, from other repositories
personal-ip-knowledge-builder
A tool for turning interviews, chats, résumés, public content, business materials, case studies, and existing documents into a long-term personal knowledge base for an AI-assisted public profile.
campaign-operations-knowledge-builder
A campaign-operations knowledge base that organizes campaign goals, user journeys, channel responsibilities, materials, timing, risk plans, and review findings.
organization-knowhow-knowledge-builder
A tool for turning team procedures, delivery processes, responsibilities, project reviews, FAQs, decision rules, and escalation steps into an AI-ready knowledge base.
skill-authoring
Create, revise, or remove reusable procedural and interactive skills; use memorystore for facts and preferences.
index-atomic-notes
Index an atomic note in existing maps of content and find potential connections to related atomic notes.
agentic-storage
Agentic storage architecture — persistent memory for AI agents using MCP, immutable versioning, sandboxing, and intent validation. Covers the stateless problem in LLM agents, RAG limitations (read-only), MCP protocol (JSON-RPC, resources, tools), storage safety layers, and agent file system design. Source: IBM…