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 advenimus/syncromsp-mcp --skill syncromspgit clone --depth 1 https://github.com/advenimus/syncromsp-mcpWrote 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/advenimus/syncromsp-mcp/syncromsp)<a href="https://agentmods.dev/skills/advenimus/syncromsp-mcp/syncromsp"><img src="https://agentmods.dev/badge/skills/advenimus/syncromsp-mcp/syncromsp/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/advenimus/syncromsp-mcp/syncromsp"><img src="https://agentmods.dev/badge/skills/advenimus/syncromsp-mcp/syncromsp.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.00081 | $0.01857 |
| Opus 5.5 | $0.00032 | $0.00743 |
| Sonnet 5.5 | $0.00016 | $0.00371 |
| Haiku 4.5 | $0.00008 | $0.00186 |
Grade A, and why
syncromsp 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 28d 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 — 122 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SyncroMSP
This skill governs how to work with SyncroMSP — the PSA/RMM platform IT MSPs use to run their business: tickets, billing, customers, scheduling, RMM, products, contracts. It applies whenever the user asks anything related to PSA/MSP workflows, regardless of whether they explicitly mention SyncroMSP.
When to invoke
Invoke automatically — without asking — for any request involving:
- Tickets, comments, labor/time tracking, line items
- Customers, contacts, leads, contracts
- Invoices, estimates, payments, recurring billing
- Appointments, scheduling
- Assets, RMM alerts, patches, running scripts on devices
- Products, inventory, purchase orders, vendors
- Wikis, worksheets, canned responses
First-run setup
On first use in any new environment, discover and cache MSP-specific identifiers. Read config.json next to this skill if it exists; otherwise create it from config.example.json and populate by API discovery.
Values to discover:
| Key | How to discover | Why |
|---|---|---|
subdomain |
Ask the user, or extract from any Syncro URL they paste | Used for clickable hyperlinks |
base_url |
https://{subdomain}.syncromsp.com (or .shield.syncromsp.com for legacy accounts — confirm with user) |
Used for clickable hyperlinks |
user_id |
Call admin_get_me |
Default assignee on tickets/appointments |
labor_products |
Call admin_list_items and filter for service-type items, or products_list and match on names like Labor / Project Labor / Remote Support / After Hours / Rush / Contract / Trip Charge |
Required for labor logging |
appointment_types |
Call appointments_list_types |
Required when scheduling |
If discovery fails for any value, ask the user once, save the answer, and proceed. Never fail silently — write what you have to config.json so the next session doesn't repeat the work.
Hyperlink rule (always)
When referencing any SyncroMSP record in chat output, ALWAYS render it as a clickable markdown link using the cached base_url:
What ships with it
11 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- config.example.json 1.1 KB
- learnings/README.md 2.5 KB
- learnings/syncro-text-fields-are-plain-text.md 3.8 KB
- README.md 5.7 KB
- references/api-quirks.md 5.3 KB
- references/appointments.md 1.9 KB
- references/billing.md 6.5 KB
- references/customers.md 2.7 KB
- references/rmm-and-assets.md 5.2 KB
- references/tickets.md 6.2 KB
- references/time-tracking.md 5.5 KB
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.
- 28d ago Changed · +2 tokens per session 184d2bbbde3d
- 1mo ago First seen · 122 lines · 79 tokens per session scan A 3176b57d7a8e
syncromsp is a skill published in the GitHub repository advenimus/syncromsp-mcp (10 stars, last pushed 27d ago), licensed MIT. It adds 81 tokens to every session and 1,857 once invoked, about $0.0003 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
story-readiness
Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
handle-linkedin-connection-request-signal
Use this skill when someone sends a team member an inbound LinkedIn connection request. An inbound request is a deliberate, ACTIVE first-party intent signal — meaningfully stronger than a passive profile view — and it deserves different scoring rules. The skill resolves and enriches the requester, gates them through…
remove
Remove a deployed framework or addon from the current workspace.