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 DanialDaeHyunNam/omniscitus --skill handoffgit clone --depth 1 https://github.com/DanialDaeHyunNam/omniscitusWrote 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/danialdaehyunnam/omniscitus/handoff)<a href="https://agentmods.dev/skills/danialdaehyunnam/omniscitus/handoff"><img src="https://agentmods.dev/badge/skills/danialdaehyunnam/omniscitus/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/danialdaehyunnam/omniscitus/handoff"><img src="https://agentmods.dev/badge/skills/danialdaehyunnam/omniscitus/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.00088 | $0.01336 |
| Opus 5 | $0.00044 | $0.00668 |
| Sonnet 5 | $0.00018 | $0.00267 |
| Haiku 4.5 | $0.00009 | $0.00134 |
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 10d 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 — 150 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Handoff — Continuation Prompt for the Next Session
Produce a single, copy-paste-ready prompt that lets a fresh session (after
/clear) continue this work with all the context this session accumulated.
This skill does not clear the context itself — that is a user action. It hands you the perfect prompt to paste into the next session. The flow is:
/handoff → copy the printed block → /clear → paste
When to Use
- User types
/handoff - User says "핸드오프", "인계 프롬프트", "다음 세션 이어가게 프롬프트 줘", "hand off"
- Context window is filling up, or Claude suggested starting a fresh session, and the user wants to continue the same work without losing state.
Golden path: run /wrap-up first (so a durable history unit exists to point
to), then /handoff.
Instructions
Step 1: Identify the work in focus
Establish what the next session should continue:
- Run
git diff --name-onlyandgit diff --cached --name-onlyto see what this session touched. - Review the conversation for the active task — what was being built, what was just finished, what is still open.
Step 2: Locate the backing history unit
Read .omniscitus/history/_index.yaml.
- Find the
status: openunit(s) whoselast_updatedis today — that is the record for this session's work. Note itsfile:path; it becomes the "full context" pointer inside the handoff prompt. - If no open unit was updated today, this session likely isn't recorded
yet. Do not block — generate the handoff anyway, but:
- In the output, replace the file pointer with a note:
⚠️ Not yet recorded — run /wrap-up first so the next session has a durable record to read. - Add a one-line suggestion after the block recommending
/wrap-upbefore/clear.
- In the output, replace the file pointer with a note:
If multiple open units were updated today, use the one matching the active task; list the others' paths as secondary pointers.
Step 3: Distill the carry-over context
Pull from the unit's ## Context, ## Pending, and latest ## Timeline
entry, plus the live conversation. Compress into:
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.
- 10d ago First seen · 150 lines · 88 tokens per session scan A 4bed841f9118
handoff is a skill published in the GitHub repository DanialDaeHyunNam/omniscitus (5 stars, last pushed 1mo ago), licensed MIT. It adds 88 tokens to every session and 1,336 once invoked, about $0.0004 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…