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/agent-loopnpx skills add MIK-HEAL/SyncPoint --skill agent-loopgit clone --depth 1 https://github.com/MIK-HEAL/SyncPointWhat 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.00041 | $0.00354 |
| Opus 5 | $0.00020 | $0.00177 |
| Sonnet 5 | $0.00008 | $0.00071 |
| Haiku 4.5 | $0.00004 | $0.00035 |
Grade A, and why
agent-loop 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.
What it actually says
Agent Orchestration Loop
The core SyncPoint cycle: boot → claim resources → work → checkpoint → handoff or resume.
Step 1: Boot the Loop
syncpoint loop boot --task <taskId> --agent <agentId>
syncpoint loop status
Step 2: Claim Resources
Declare what files/resources you will touch before editing:
syncpoint claim <file> --agent <agentId> --task <taskId>
syncpoint status
If a SyncGate is created due to conflict, use /syncpoint-ai-skill:sync to resolve it.
Step 3: Work and Checkpoint
Do your work, then save progress:
syncpoint loop checkpoint --task <taskId> --agent <agentId>
syncpoint checkpoint list --task <taskId>
Step 4: Handoff or Resume
Transfer to another agent:
syncpoint loop handoff --task <taskId> --agent <agentId> --target <otherAgentId>
Or resume from latest checkpoint:
syncpoint loop resume --task <taskId> --agent <agentId>
Step 5: Release Resources
syncpoint release <file> --agent <agentId>
syncpoint release --task <taskId> --agent <agentId>
Verification
syncpoint loop status
syncpoint status
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 · 60 lines · 41 tokens per session scan A 8664e8400669
agent-loop is a skill published in the GitHub repository MIK-HEAL/SyncPoint (5 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 41 tokens to every session and 354 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
lint-js
Lint JS/TS code only. Use before opening a PR when only JavaScript or TypeScript files were changed (no Rust).
fmt
Format all code in the repository. Run before opening a PR or committing changes.
angular-developer
Generates Angular code and provides architectural guidance. Trigger when creating projects, components, services, or HTTP communication, or for best practices on reactivity (signals, linkedSignal, resource, httpResource), forms, dependency injection, routing, SSR, accessibility (ARIA), animations, styling (component…
reference-core
Explains the mental model and architecture of the code under packages/core. You MUST use this skill any time you plan to work with code in packages/core.
migrate-oxfmt
Guide for migrating a project from Prettier or Biome to Oxfmt. Use when asked to migrate, convert, or switch a JavaScript/TypeScript project's formatter from Prettier or Biome to Oxfmt.
migrate-oxlint
Guide for migrating a project from ESLint to Oxlint. Use when asked to migrate, convert, or switch a JavaScript/TypeScript project's linter from ESLint to Oxlint.