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 myelixlabs/synapse-mcp --skill reviewgit clone --depth 1 https://github.com/myelixlabs/synapse-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/myelixlabs/synapse-mcp/review)<a href="https://agentmods.dev/skills/myelixlabs/synapse-mcp/review"><img src="https://agentmods.dev/badge/skills/myelixlabs/synapse-mcp/review/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/myelixlabs/synapse-mcp/review"><img src="https://agentmods.dev/badge/skills/myelixlabs/synapse-mcp/review.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.00040 | $0.00254 |
| Opus 5.5 | $0.00016 | $0.00102 |
| Sonnet 5.5 | $0.00008 | $0.00051 |
| Haiku 4.5 | $0.00004 | $0.00025 |
Grade A, and why
review 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 7d 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
Review changes
- Find the
repo_idfor the current project withsynapse_manage_repos(actionlist), matching on the project directory. If the project is not registered, stop and suggest/synapse-mcp:index. - Get the diff. Use the working tree changes (
git diff HEAD). If there are none, diff against$ARGUMENTSif the user gave a base, otherwise against the repository's main branch. - Call
synapse_change_reviewwith actionreview_diff, the diff and therepo_id. - Report the findings most serious first: what could break and why, which callers are affected, which contracts changed, and which tests to run.
Report only. Do not change any code unless the user asks.
If Synapse answers that this needs a Pro licence, say so plainly and point the user to https://synapse-mcp.dev/download. Do not retry or work around it.
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.
- 7d ago First seen · 17 lines · 40 tokens per session scan A 36d272cf718e
review is a skill published in the GitHub repository myelixlabs/synapse-mcp (3 stars, last pushed 6d ago), licensed MIT. It adds 40 tokens to every session and 254 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-09-30.
Other skills, from other repositories
enola
Use Enola when investigating architecture, dependencies, blast radius, cross-repository relationships, structural regressions, or what a code change did to the system.
trace-mcp-refactoring
Safe refactoring workflow using trace-mcp — assess risk, find candidates, check impact, and rename symbols across all files without missing import sites or cross-file references.
m1nd-first
Use when investigating a repository, searching for implementation, reviewing changes, working from specs/docs, or preparing a risky code change in an environment where m1nd is available. This doctrine makes m1nd the first investigative layer before grep, glob, or manual file reads, except when the task is pure…
qartez
Semantic code intelligence skill for qartez MCP. Use qartez tools for code exploration, impact analysis, and guarded refactors; treat built-in code-tool denials as routing signals and recover via qartez replacements.
skill-improver
Trigger: improve skills, audit skills, refactor skills, skill quality. Audit and upgrade existing LLM-first skills.
go-testing
Trigger: Go tests, go test coverage, Bubbletea teatest, golden files. Apply focused Go testing patterns.