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 jqaisystems/jqai-ai-skills --skill session-handoffgit clone --depth 1 https://github.com/jqaisystems/jqai-ai-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/jqaisystems/jqai-ai-skills/session-handoff)<a href="https://agentmods.dev/skills/jqaisystems/jqai-ai-skills/session-handoff"><img src="https://agentmods.dev/badge/skills/jqaisystems/jqai-ai-skills/session-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/jqaisystems/jqai-ai-skills/session-handoff"><img src="https://agentmods.dev/badge/skills/jqaisystems/jqai-ai-skills/session-handoff.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.00093 | $0.00661 |
| Opus 5.5 | $0.00037 | $0.00264 |
| Sonnet 5.5 | $0.00019 | $0.00132 |
| Haiku 4.5 | $0.00009 | $0.00066 |
Grade A, and why
session-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 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 — 62 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Session Handoff
Context dies between sessions. The next session re-reads files, re-discovers decisions, and re-hits the same trap that cost an hour last time. This skill freezes the session's working state into one document built to be read cold.
Step 1: Mine the session
Extract from the current conversation, not from memory of what should have happened:
- What was accomplished: only things actually finished and verified. Half-done work is listed as half-done.
- Decisions made and why: especially decisions that reversed an earlier approach. The "why" is the part the next session cannot reconstruct.
- What is in progress: exact state, which file, which step.
- Next steps: concrete and ordered, with the first one precise enough to start typing immediately.
- Gotchas: everything that failed and how it was fixed, environment quirks, commands that need specific flags, things that look broken but are fine.
- Key paths and commands: the files that matter and the exact commands to run (build, test, deploy, resume).
Step 2: Write the handoff
Default target: START_HERE.md in the project root (or append a dated section to an existing one, newest at the top). Format:
# Start Here: <date>
## TL;DR
Two sentences: where the project is, and the single next action.
## Done this session
## In progress
Exact state, file, and step for each item.
## Next steps (in order)
1. The first one must be executable immediately, with the exact command or file.
## Decisions and why
## Gotchas
What burned time this session, so it does not burn time again.
## Key paths and commands
Step 3: Verify readability cold
Reread the document as someone with zero context: no session shorthand, no "the fix we discussed", no codenames invented mid-conversation. Every reference names its file. If a next step depends on a decision, the decision is in the document too.
On resume
When a new session starts with "where did we leave off": read START_HERE.md, confirm the state still matches reality (files may have changed since), and start on next step 1. Flag divergence instead of following a stale plan.
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.
- 1mo ago First seen · 62 lines · 93 tokens per session scan A 62f1fac82ef6
session-handoff is a skill published in the GitHub repository jqaisystems/jqai-ai-skills (3 stars, last pushed 13d ago), licensed MIT. It adds 93 tokens to every session and 661 once invoked, about $0.0004 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
baoyu-wechat-summary
Summarizes WeChat group chat highlights into a structured digest using the local wx-cli binary (https://github.com/jackwener/wx-cli). Generates a normal digest by default; a roast (毒舌) version is opt-in. Maintains per-group history (history.json + history-digests.jsonl), per-user profiles, and per-group fact memory…
wordpress-editing-safety
Safety rules for editing a WordPress site through Respira. Use whenever the user mentions WordPress, Respira, editing a page or a site, a page builder, a snapshot, a duplicate, an approval, or rolling back. Covers read before write, duplicates on live pages, verifying every write, reading state before a retry…
respira-workflow
Sets the posture for working on a WordPress site through Respira: report what changed on the site, stay visible during long operations, be honest about limits, and send what Respira cannot do to the founder. Use whenever Respira is mentioned, the user references their WordPress site, or the user wants to edit a site.
kelly-email
Busabase AirApp-first email inbox-zero operator for reviewing unread mail, drafting replies, approving archive/mark-read/send actions, and executing only explicitly approved mailbox changes across configured accounts. Use when the user invokes $kelly-email, asks to process unread email, configure an email account…
kelly-messenger
Unified chat inbox (Busabase App-in-Skill) aggregating WhatsApp, Discord, Slack, and Telegram messages into one place with a reply queue. Use when the user invokes $kelly-messenger or /kelly-messenger, wants a unified inbox, chat aggregation, to read WhatsApp/Discord/Slack/Telegram messages in one place, review…
macos-app-multi-instances
Run several simultaneous instances of one macOS app (e.g. two or three accounts logged into WeChat at once) by duplicating and re-signing its .app bundle. Use when an app refuses to open a second window and just refocuses the running one, when open -n -a launches no new process, or when a second independent login…