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/mik-heal/syncpoint/handoffnpx skills add MIK-HEAL/SyncPoint --skill handoffgit clone --depth 1 https://github.com/MIK-HEAL/SyncPointWrote 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/mik-heal/syncpoint/handoff)<a href="https://agentmods.dev/skills/mik-heal/syncpoint/handoff"><img src="https://agentmods.dev/badge/skills/mik-heal/syncpoint/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 | $0.00036 | $0.00249 |
| Opus 5 | $0.00018 | $0.00125 |
| Sonnet 5 | $0.00007 | $0.00050 |
| Haiku 4.5 | $0.00004 | $0.00025 |
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 4d 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
Agent Handoff
Step 1: Create Checkpoint
syncpoint loop checkpoint --task <taskId> --agent <sourceAgentId>
syncpoint checkpoint list --task <taskId>
Step 2: Initiate Handoff
syncpoint loop handoff --task <taskId> --agent <sourceAgentId> --target <targetAgentId>
syncpoint handoff create --task <taskId> --from <sourceAgentId> --to <targetAgentId>
Step 3: Accept or Reject
syncpoint handoff accept <handoffId>
syncpoint handoff reject <handoffId> --reason "Not my domain"
Step 4: Resume
syncpoint loop resume --task <taskId> --agent <targetAgentId>
syncpoint loop status
Verification
syncpoint loop status
syncpoint status --task <taskId>
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.
- 4d ago First seen · 40 lines · 36 tokens per session scan A 57fc3ac0e152
handoff is a skill published in the GitHub repository MIK-HEAL/SyncPoint (5 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 36 tokens to every session and 249 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-31.
Other skills, from other repositories
gh-file-issue
Use when filing a new Codewhale GitHub issue: turn a bug or idea into a well-formed, actionable issue with repro, acceptance criteria, labels, and milestone.
gh-treasure-hunt
Hunt the issue/PR queue for highest value-over-risk wins: clean focused community PRs, already-implemented issues to close, safe quick-fixes.
gh-assign-issues
Use to assign GitHub issues to a milestone and/or owners in bulk, verifying each.
google-agents-cli-deploy
This skill should be used when the user wants to "deploy an agent", "deploy my ADK agent", "set up CI/CD", "configure secrets", "troubleshoot a deployment", or needs guidance on Agent Runtime, Cloud Run, or GKE deployment targets, or binding an agent to an Agent Gateway. Covers deployment workflows, service accounts…
google-agents-cli-eval
This skill should be used when the user wants to "run an evaluation", "evaluate my agent", "evaluate my ADK agent", "write an eval dataset", "analyze eval failures", "compare eval results", "optimize agent", or needs guidance on the Agent Platform eval methodology and the Quality Flywheel. Covers eval metrics, dataset…
google-agents-cli-workflow
This skill should be used when the user wants to "develop an agent", "build an agent using ADK", "run the agent locally", "debug agent code", "test an agent", "deploy an agent", "publish an agent", "monitor an agent", or needs the ADK (Agent Development Kit) development lifecycle and coding guidelines. Entrypoint for…