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 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/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/mik-heal/syncpoint/handoff"><img src="https://agentmods.dev/badge/skills/mik-heal/syncpoint/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.00036 | $0.00294 |
| Opus 5.5 | $0.00014 | $0.00118 |
| Sonnet 5.5 | $0.00007 | $0.00059 |
| Haiku 4.5 | $0.00004 | $0.00029 |
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 11d 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> --summary "Progress summary"
syncpoint loop status --agent <sourceAgentId> --task <taskId>
Step 2: Initiate Handoff
syncpoint loop handoff --task <taskId> --from <sourceAgentId> --to <targetAgentId> --context "Handoff summary"
syncpoint handoff create --task <taskId> --from <sourceAgentId> --to <targetAgentId> --context "Handoff summary"
Step 3: Accept or Reject
syncpoint handoff accept <handoffId>
syncpoint handoff reject <handoffId>
Step 4: Resume
syncpoint loop resume --task <taskId> --agent <targetAgentId>
syncpoint loop status --agent <targetAgentId> --task <taskId>
Verification
syncpoint loop status --agent <targetAgentId> --task <taskId>
syncpoint sync 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.
- 11d ago Changed c390b35d22ef
- 1mo ago First seen · 40 lines · 36 tokens per session scan A 57fc3ac0e152
handoff is a skill published in the GitHub repository MIK-HEAL/SyncPoint (6 stars, last pushed 10d ago), licensed Apache-2.0. It adds 36 tokens to every session and 294 once invoked, about $0.0001 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
ponytail-debt
Harvest every ponytail: comment in the codebase into a debt ledger, so the deliberate shortcuts and deferrals ponytail leaves behind get tracked instead of rotting into "later means never". Use when the user says "ponytail debt", "/ponytail-debt", "what did ponytail defer", "list the shortcuts", "ponytail ledger", or…
pi-review-gated-delivery
Use when coordinating review-gated delivery of discrete GitHub issues between one implementation peer and a review-only lead, with user-owned Changesets and approval-gated commits.
pstack-why
Use for 'why does X work this way', 'why we picked Y', design rationale, regressions, postmortems, or data-backed thresholds. Discovers available MCPs and queries each evidence category (source control, issue tracker, long-form docs, real-time chat, infrastructure observability, error tracking, product analytics…
create-issue
Draft and submit a GitHub issue from a user idea or bug description, with bilingual body and correct labels.
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.