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 jackfranklin/dotfiles --skill handoffgit clone --depth 1 https://github.com/jackfranklin/dotfilesWrote 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/jackfranklin/dotfiles/handoff)<a href="https://agentmods.dev/skills/jackfranklin/dotfiles/handoff"><img src="https://agentmods.dev/badge/skills/jackfranklin/dotfiles/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/jackfranklin/dotfiles/handoff"><img src="https://agentmods.dev/badge/skills/jackfranklin/dotfiles/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.00034 | $0.01186 |
| Opus 5.5 | $0.00014 | $0.00474 |
| Sonnet 5.5 | $0.00007 | $0.00237 |
| Haiku 4.5 | $0.00003 | $0.00119 |
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 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 — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Handoff & Session Management
Use this skill when you want to summarize, save, or resume the state of your work. It supports three distinct operations based on the user's request:
- Save / Update Handoff: Write/update a progress summary file in
.jai/. - Search / List Handoffs: Scan
.jai/to find and resume work from a previous session. - Summarize: Generate a scannable conversation summary directly in the chat window.
1. Save / Update Handoff
Use when the user wants to "save progress", "update the handoff", or "write a handoff".
- Determine if this handoff represents a long-lived project plan (e.g., architecture, roadmap spanning multiple weeks/conversations) or a short-lived conversation handoff (capturing state for the next session). If the context makes this distinction unclear, ask the user for clarification.
- Generate a very short name for this task/plan if not already established (e.g.,
setup-handoff-skill). - Determine the target folder and file name format based on the category:
- Project Plan: Save to
.jai/plans/<short-name>.md. - Conversation Handoff: Save to
.jai/conversations/YYYY-MM-DD-<short-name>.md.
- Project Plan: Save to
- Check if a matching file already exists in the target subdirectory.
- If an existing file is found:
- Read its content to understand the current state.
- If the file is large (e.g., > 100 lines), ask the user for permission to append or if they prefer creating a new file.
- When updating, prefer appending new information to the relevant sections rather than replacing existing content.
- Prefix all updates with a timestamp (e.g.,
[2026-06-01 11:49]).
- If creating a new file or appending to an existing one, ensure the content covers:
- Summary: A single-line summary of the current state and goal.
- Original Goal: What was the user trying to achieve?
- Current Status: What has been completed so far?
- Next Steps: High-level objectives or next areas of focus.
- Key Decisions & Context: Non-obvious decisions or important context.
- Relevant Files: Files created, modified, or central to the task.
- Ensure the target directory exists before writing.
- Inform the user that the handoff or plan has been recorded/updated and provide the file path.
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 · 73 lines · 34 tokens per session scan A 92af1c5c47cd
handoff is a skill published in the GitHub repository jackfranklin/dotfiles (254 stars, last pushed 6d ago), licensed MIT. It adds 34 tokens to every session and 1,186 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-30.
Other skills, from other repositories
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
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…
shellm
Reference for the shellm system — recursive LLM shell, identity management, memory, skills, trajectory, and all CLI tools. Use when working on shellm itself, debugging agent behavior, or understanding how the pieces fit together.