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 agentmods add skills/thewinci/mimirs/handoffnpx skills add TheWinci/mimirs --skill handoffgit clone --depth 1 https://github.com/TheWinci/mimirsWrote 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/thewinci/mimirs/handoff)<a href="https://agentmods.dev/skills/thewinci/mimirs/handoff"><img src="https://agentmods.dev/badge/skills/thewinci/mimirs/handoff.svg" alt="Measured on agentmods" 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.00061 | $0.00308 |
| Opus 5 | $0.00030 | $0.00154 |
| Sonnet 5 | $0.00012 | $0.00062 |
| Haiku 4.5 | $0.00006 | $0.00031 |
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 6d 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
Handoff
Goal: leave the project state recorded so the next session starts from catch-up, not from scratch. The end-of-session counterpart to catch-up.
- Snapshot what changed —
git_contextfor the modified/uncommitted files and recent commits, so the handoff names the exact files touched this session. - Record caveats —
annotateany fragile spot, constraint, race, or workaround you discovered or introduced this session, on the file it lives in;get_annotationson the touched files to confirm earlier notes still hold (delete_annotationones a fix made stale). - Record the decision & next step —
create_checkpoint(typehandoff) with what was done, which files changed, why, and the concrete next action. Keep the summary tight (it has a length cap). If the session was a dead end or a direction change, say so and why.
Finish: a short handoff note — done / in flight / next step / open caveats — each with a file:line or checkpoint reference, so a fresh session can resume without re-deriving context.
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.
- 6d ago First seen · 15 lines · 61 tokens per session scan A fdfdce754c06
handoff is a skill published in the GitHub repository TheWinci/mimirs (29 stars, last pushed 21d ago), licensed Apache-2.0. It adds 61 tokens to every session and 308 once invoked, about $0.0003 per session on Opus 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
context-efficient-coding
Use ContextFlux to minimize coding-agent context and tool calls when exploring, planning, debugging, reviewing, or modifying an unfamiliar or multi-file repository. Trigger for codebase discovery, symbol search, architecture questions, cross-file changes, error tracing, review feedback, test discovery, or any request…
tally-webhooks
Receive and verify Tally webhooks. Use when setting up Tally form webhook handlers, debugging Tally-Signature verification, or handling FORMRESPONSE submission events and reading answers from data.fields.
opencode-export
Export opencode sessions to self-contained HTML + JSON archives for sharing, review, or backup. Use when the user wants to save, archive, or share their AI coding session history.
wiki-dashboard
Create dynamic, queryable dashboard views of the Obsidian vault using Obsidian Bases or Dataview. Use this skill when the user says "create a dashboard", "vault dashboard", "show all X as a table", "dynamic view", "query my vault", "build a content index", "show me all concepts/entities/projects", or wants a…
codex-skin-pack-installer
Install Codex themes and Codex skin packs with npx skills. Use this skill when a user wants Codex to find, download, validate, apply, switch, remix, or restore Codex desktop themes such as caishen-readable, caishen-lite, mythic-guardian-noir, global-founder-bright, export-night, or caishen-max. It stages verified…
om-build-workflow
Build or extend standalone business workflows, activities, event triggers, durable user tasks, compensation, output paths, idempotency, and live progress. Use for "add workflow", "custom activity", "CALLAPI", "approval task", "workflow progress", or "zbuduj workflow".