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/abdurrafay2004/handoff/setupnpx skills add AbdurRafay2004/handoff --skill setupgit clone --depth 1 https://github.com/AbdurRafay2004/handoffWhat 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 | $0.00102 | $0.01229 |
| Opus 5 | $0.00051 | $0.00615 |
| Sonnet 5 | $0.00020 | $0.00246 |
| Haiku 4.5 | $0.00010 | $0.00123 |
Grade A, and why
setup 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 2d 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 — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Set up handoff in this repo
Scaffold the durable project-memory system, then populate it from the real codebase so it ships useful — not blank. Discovery drafts; the user confirms before anything is saved. Never invent project facts (RULES rule 5).
0. Locate templates & detect existing install
- The template tree is bundled with this plugin at
../../templates/relative to this skill file (i.e.<plugin-root>/templates/). Resolve that absolute path. - Check whether
.handoff/already exists in the project root:- Exists → do NOT overwrite. Tell the user it's already set up; offer to refresh specific files (e.g. re-run discovery for STATUS/MAP/TECH_STACK) or seed a CONTEXT.md. Stop here unless they choose a refresh.
- Absent → continue.
1. Copy the template tree
Copy the bundled templates/ into the project as .handoff/, preserving
structure (BOOT, RULES, STATUS, MAP, CHANGELOG, context/, docs/ with
SKILL-WORKFLOW.md, tasks/ with inbox/now/done). Keep the .gitkeep files.
Do not edit RULES' universal section.
Write the current plugin version into .handoff/VERSION (single line) — the
SessionStart hook uses it for template-drift detection.
2. Guided discovery (read the repo — do not guess)
Read what actually exists, quietly:
- Build/manifest files:
package.json,pyproject.toml,go.mod,Cargo.toml,composer.json,Gemfile, Makefile, CI config, framework config files. - Top-level directory layout and the largest/most-central source folders.
git log --oneline -20and current branch for recent direction.- Any existing README for product intent. Derive: project name, type, primary stack, common commands (build/dev/test/lint), deploy target, and the verify commands for RULES rule 10.
3. Draft, then CONFIRM before saving
Present concise drafts for the user to correct:
- STATUS.md — Current State (where the repo stands now), Active Work (none unless evident), Blockers (none unless evident). Keep ≤ 25 lines.
- context/TECH_STACK.md — stack, commands, env vars, deploy, verify commands.
- MAP.md — entry points, key directories, where to make common changes.
- context/PRODUCT.md — only if a README/product intent is discoverable; otherwise leave the template prompts and say so.
- Replace the
<PROJECT_NAME>/<PROJECT_TYPE>/<PRIMARY_STACK>placeholders in BOOT.md. Wait for the user's confirmation/edits. Only then write the files. For anything you cannot determine from the repo, leave the template prompt in place rather than inventing — and tell the user what you left blank.
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.
- 2d ago First seen · 88 lines · 102 tokens per session scan A 8ecb2858999e
setup is a skill published in the GitHub repository AbdurRafay2004/handoff (4 stars, last pushed 1mo ago), licensed MIT. It adds 102 tokens to every session and 1,229 once invoked, about $0.0005 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
checkpoint
Write the current working state (task, decisions, files touched, open problems, next steps) to .amber/STATE.md so it survives compaction and session restarts. Use when the user asks to checkpoint/save state, before risky long operations, when context feels heavy, or before ending a work session.
focus
Declare a focus contract for the current task to keep context lean — scopes which files/dirs are in play, bans out-of-scope exploration, and routes broad searches to subagents. Use when starting a task, when the user says "focus on X", or when the session is drifting across unrelated parts of the codebase.
react
React UI patterns for apps/ui—Effects vs rendering, TanStack Query for all server data, useMemo, keys, event handlers. Start here when creating or editing React components.
diet
Audit what is eating the context window in this project (CLAUDE.md size, MCP servers, rules that should be skills) and produce a concrete slimming plan with estimated token savings. Use when the user complains about context filling up fast, frequent compaction, or asks to optimize/reduce context usage.
resume
Reload saved working state from .amber/ (STATE.md, FOCUS.md, checkpoint.md) and continue the previous task. Use when the user says resume/continue where we left off, or at the start of a session in a project that has an .amber directory.
project-memory
Use when resuming work after chat loss, switching AI models, migrating context to a new agent or workspace, or maintaining long-running research and project memory across sessions. Manages roadmap, decision log, hypotheses, research evidence, and recovery checkpoints as separate canonical files so no single transcript…