Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/MIK-HEAL/SyncPointnpx agentmods add skills/mik-heal/syncpoint/setupWrote 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/setup)<a href="https://agentmods.dev/skills/mik-heal/syncpoint/setup"><img src="https://agentmods.dev/badge/skills/mik-heal/syncpoint/setup/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/setup"><img src="https://agentmods.dev/badge/skills/mik-heal/syncpoint/setup.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.00038 | $0.00587 |
| Opus 5.5 | $0.00015 | $0.00235 |
| Sonnet 5.5 | $0.00008 | $0.00117 |
| Haiku 4.5 | $0.00004 | $0.00059 |
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 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.
How it starts
The opening of the file, as written. The whole thing — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SyncPoint Setup
You are helping a user set up SyncPoint for AI agent coordination. Follow these steps.
Prerequisites
- Node.js >= 20
- Git repository initialized
Step 1: Install SyncPoint
Install the core package globally before doing anything else. This is the first action the agent should take when SyncPoint is needed:
npm install -g syncpoint-ai
If syncpoint is not on PATH yet, do not continue until the install succeeds.
Step 2: Initialize the Project
cd <project-directory>
syncpoint init
This creates a .syncpoint/ directory with a SQLite database. To generate a team from a template:
syncpoint init --team pair
syncpoint init --team squad
Available team templates: pair, trio, squad, review-team.
Step 3: Create Agent Manifests
Every AI agent needs a manifest file declaring its identity, provider, role, and capabilities.
Interactive creation:
syncpoint agent init
Or import from existing manifests:
syncpoint agent import ./manifests/
View all declared agents:
syncpoint agent list
Step 4: Start the Server
syncpoint server start
syncpoint server start --port 9876
Sync declared agents into runtime:
syncpoint agent sync
Step 5: Verify Everything Works
syncpoint status
syncpoint agent list --runtime
syncpoint dev status
Next Steps
- Create a task:
syncpoint task create "My Task" - Boot the agent loop: see
/syncpoint-ai-skill:agent-loop - Claim resources: see
/syncpoint-ai-skill:claim
Agent Behavior
- Only install
syncpoint-aiafter the user asks to set up or enable SyncPoint. - After installation, verify that
syncpoint --versionsucceeds before continuing. - If installation fails or
syncpointis not on PATH, stop and report the failure.
Troubleshooting
| Problem | Solution |
|---|---|
| Port 8765 in use | syncpoint server start --port 9876 |
| Agents not in runtime | syncpoint agent sync |
| Database locked | Wait 5s; if persistent, restart the server |
| Migration errors | v0.2 is a breaking reset — delete .syncpoint/syncpoint.db and re-run syncpoint init |
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 3f41dbc22fa4
- 1mo ago First seen · 95 lines · 38 tokens per session scan A 2d61470673d4
setup is a skill published in the GitHub repository MIK-HEAL/SyncPoint (6 stars, last pushed 10d ago), licensed Apache-2.0. It adds 38 tokens to every session and 587 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
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.