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 SNIKO/agent-skills --skill handoff-sessiongit clone --depth 1 https://github.com/SNIKO/agent-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/sniko/agent-skills/handoff-session)<a href="https://agentmods.dev/skills/sniko/agent-skills/handoff-session"><img src="https://agentmods.dev/badge/skills/sniko/agent-skills/handoff-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/sniko/agent-skills/handoff-session"><img src="https://agentmods.dev/badge/skills/sniko/agent-skills/handoff-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.00029 | $0.00861 |
| Opus 5.5 | $0.00012 | $0.00344 |
| Sonnet 5.5 | $0.00006 | $0.00172 |
| Haiku 4.5 | $0.00003 | $0.00086 |
Grade A, and why
handoff-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.
What it actually says
<decision_rules>
- Prefer precise session facts over general project descriptions.
- Include only items touched, created, decided, started, or made relevant in this session.
- If a required section has no information, write
none; never omit required sections. - Use absolute paths for files, directories, worktrees, plans, and memory artifacts when a path is known. If only a relative path is known, resolve it against the current working directory before writing it.
- If a plan or task list drove the session, list it first under
Key files for next session. - For running state, include how the next agent can stop or resume the process when that information is known.
- If evidence is uncertain or unavailable, say so briefly instead of inventing state. </decision_rules>
<output_format> Use exactly this structure every time:
# Session Handoff — <one-line title of what this session was about>
## Where it started
<2-3 sentences: what the user asked for, key framing or constraints that emerged>
## Decisions locked + what shipped
- <decision or change> — <why it matters, and where it lives if applicable>
- ...
## Key files for next session
- `<absolute path>` — <why the next agent should read this first>
- Plan file: `<absolute path>` — <if a plan drove the session, otherwise `none`>
- Notes or memory touched: `<absolute path>` — <if any, otherwise `none`>
## Key facts for next session
- <fact> — <why it matters>
- ...
## Deferred + open questions
- Deferred: <item> — <why pushed to later>
- Open: <question needing user input> — <context>
## Pick up here
<leave empty, will be filled by the user>
</output_format>
<completion_criteria> Before sending, verify that:
- Every required section is present.
- No section contains invented or assumed state.
- All known file paths are absolute.
- Running processes, ports, worktrees, and branches are explicit or marked
none. - Verification commands are specific and tied to expected or observed outcomes.
Pick up herecontains one focused next action. </completion_criteria>
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 · 91 lines · 29 tokens per session scan A 119894a191fa
handoff-session is a skill published in the GitHub repository SNIKO/agent-skills (2 stars, last pushed 2mo ago), licensed MIT. It adds 29 tokens to every session and 861 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
html-artifacts
Author the HTML for a plan artifact, dashboard iframe, or Slack attachment — structure, design plan, available runtime, theming, and craft. Read this before writing HTML for publishartifact, outputiframe, or slackattachhtml.
baby-sit
Monitor a GitHub pull request until CI is green, diagnose failures, and rerun only evidence-backed flaky GitHub Actions jobs.
workspaces
How an Open SWE workspace's sandbox image works and how to change it — create one, edit or fork an existing one, start from scratch, what setupscript and updatescript are for, why a nightly refresh failed, where the build logs are, and how to read a rebuild in progress. Read this whenever someone asks about…
linear-tickets
Create or update high-quality Linear tickets while preserving the originating report, diagnostic links, attachments, and reporter/requester attribution. Read this whenever someone asks to create, recreate, or update a Linear issue.
oracle
Oracle second-model review: bundle prompts/files, debug, refactor, design.
oracle-advisor
Request a second-model consultation with explicit API, browser, or render transport and per-run provenance. Use when transport choice or model/effort evidence is part of the request; the existing oracle skill remains the browser-first workflow.