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 Advai-X/advai-skills --skill advai-handoffgit clone --depth 1 https://github.com/Advai-X/advai-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/advai-x/advai-skills/advai-handoff)<a href="https://agentmods.dev/skills/advai-x/advai-skills/advai-handoff"><img src="https://agentmods.dev/badge/skills/advai-x/advai-skills/advai-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/advai-x/advai-skills/advai-handoff"><img src="https://agentmods.dev/badge/skills/advai-x/advai-skills/advai-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.00045 | $0.00726 |
| Opus 5 | $0.00023 | $0.00363 |
| Sonnet 5 | $0.00009 | $0.00145 |
| Haiku 4.5 | $0.00005 | $0.00073 |
Grade A, and why
advai-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 12d 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 — 94 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Advai Handoff
Use this skill to persist a compact session handoff in the current project and restore that context later from .advai/HANDOFF.md.
When to Invoke
Invoke this skill when the user wants to:
- Record what has been done in the current conversation for the next agent session
- Save the current task goal, progress, changed files, validation status, and next step
- Resume work in a new conversation by reading the previous handoff note first
- Maintain a lightweight project-local state file instead of relying on long chat history
Do not use this skill for general documentation, changelogs, or long-form project notes.
Handoff File
- Use exactly one file:
.advai/HANDOFF.md - Treat the current project directory as the storage scope
- Create the
.advai/directory if it does not already exist - Do not introduce extra handoff files, dated snapshots, or nested handoff directories unless the user explicitly asks for them
Operating Flow
In an active conversation
When the user asks to record or update handoff state:
- Read the current
.advai/HANDOFF.mdif it exists. - Refresh the file with the latest state of the current task.
- Keep the note concise, factual, and easy for the next session to scan.
In a new conversation
When the user asks to resume from a previous handoff:
- Check whether
.advai/HANDOFF.mdexists in the current project. - Read it before making assumptions about prior progress.
- Summarize the handoff back to the user and continue from the recorded next step.
- If the file is missing, say that no prior handoff note was found and continue with normal discovery.
Recommended Template
Use this structure unless the user requests a different format:
# Handoff
## Goal
- <current objective>
## Completed
- <finished work>
## Changed Files
- `<path>`: <what changed>
## Validation
- <tests run, checks performed, or not run yet>
## Open Issues
- <known gaps, blockers, or follow-ups>
## Next Step
- <the most useful next action>
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.
- 12d ago First seen · 94 lines · 45 tokens per session scan A 4eaf8424b5cf
advai-handoff is a skill published in the GitHub repository Advai-X/advai-skills (64 stars, last pushed 17d ago), licensed MIT. It adds 45 tokens to every session and 726 once invoked, about $0.0002 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
media-ingest
Ingest video, audio, PDF, book, screenshot, and GitHub repo content into the brain. Multi-format handling with entity extraction and backlink propagation. Covers video-ingest, youtube-ingest, and book-ingest subtypes.
mem0-oss-to-platform
Plan and then execute a migration of a project from the mem0 open-source / self-hosted SDK (the local Memory class) to the mem0 Platform / hosted / managed SDK (the MemoryClient class). Use this whenever a developer wants to move, switch, or migrate their mem0 usage off OSS/self-hosted to the hosted API — e.g.…
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…
establishing-project-context
Use when the user asks to establish shared project language, or project work exposes a conflicting, renamed, or deprecated domain term that needs active semantic modeling. Routine small tasks stay on the fast path.