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 pktikkani/agent-skills --skill handoffgit clone --depth 1 https://github.com/pktikkani/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/pktikkani/agent-skills/handoff)<a href="https://agentmods.dev/skills/pktikkani/agent-skills/handoff"><img src="https://agentmods.dev/badge/skills/pktikkani/agent-skills/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/pktikkani/agent-skills/handoff"><img src="https://agentmods.dev/badge/skills/pktikkani/agent-skills/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.00045 | $0.00770 |
| Opus 5.5 | $0.00018 | $0.00308 |
| Sonnet 5.5 | $0.00009 | $0.00154 |
| Haiku 4.5 | $0.00005 | $0.00077 |
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 — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Handoff — write STATUS.md
Write (or fully overwrite) STATUS.md at the current project root — create it if
absent. It is a SNAPSHOT, not a log: full overwrite every time, never append.
Target ≤120 lines / ~1-2k tokens.
Template (fixed sections, in this order)
# STATUS — <project> — <YYYY-MM-DD>
## Now
What's in flight; the exact next 1-3 actions, with file paths.
## State
What works, what's broken, test status.
## Decisions this session
Only NEW decisions, each with a one-line why. Durable ones should graduate to
BLUEPRINT.md/ADRs — note explicitly when one should.
## Gotchas
Non-obvious traps discovered this session: env quirks, flaky commands, things
that look wrong but are right.
## Pointers
Key files:lines, running processes, external state (open PRs, pending tokens, ...).
Rules
- Concrete over narrative: paths, commands, numbers — no prose recap of the conversation.
- Nothing secret: no tokens/keys — reference their location instead (e.g. "creds in .env").
- If the repo is git-tracked, commit STATUS.md alone with message
handoff: <YYYY-MM-DD>ONLY if the user confirms. - Re-entry cost must stay under ~2k tokens. If the draft exceeds it, cut State/Decisions detail first — never Now/Gotchas.
- Do not duplicate content already captured in other artifacts (BLUEPRINT.md, ADRs, PRDs, issues, commits, diffs) — reference them by path in Pointers.
- If the user passed arguments, treat them as what the next session will focus on and weight Now accordingly.
Daybook entry
After STATUS.md is written, append one entry for this session to the project's daybook, at the path given in the user's global agent instructions (CLAUDE.md / AGENTS.md). No daybook path configured → skip this step and say so.
The daybook is the opposite of STATUS.md: a LOG, append-only. New entries go at
the bottom; never edit or reorder earlier ones. One file per month
(YYYY-MM.md) — create it with a one-line # Daybook — <project> — <YYYY-MM>
header if absent. Add the ## <date> heading only if today's is not already
the last one in the file.
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 Changed · +29 lines · +8 tokens per session dabaa76d7f82
- 2mo ago First seen · 55 lines · 37 tokens per session scan A df2a030b59e4
handoff is a skill published in the GitHub repository pktikkani/agent-skills (3 stars, last pushed 1mo ago), licensed MIT. It adds 45 tokens to every session and 770 once invoked, about $0.0002 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
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…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
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…