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 statusgit 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/status)<a href="https://agentmods.dev/skills/myelixlabs/synapse-mcp/status"><img src="https://agentmods.dev/badge/skills/myelixlabs/synapse-mcp/status/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/status"><img src="https://agentmods.dev/badge/skills/myelixlabs/synapse-mcp/status.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.00058 | $0.00433 |
| Opus 5.5 | $0.00023 | $0.00173 |
| Sonnet 5.5 | $0.00012 | $0.00087 |
| Haiku 4.5 | $0.00006 | $0.00043 |
Grade A, and why
status 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
Synapse status
Work through these in order and stop at the first thing that needs the user.
- If the Synapse tools are available, call
synapse_indexer_controlwith actionhealth. Report in one or two lines: whether the server is healthy, whether the user is signed in, and how many repositories are registered. Add one line for the tokens Synapse has saved this session and all time, from the same result. - Call
synapse_manage_reposwith actionlist. Say whether the current project is registered and how far its indexing has got. If it is not registered, suggest/synapse-mcp:index. If it is still indexing and the list does not say enough, callsynapse_indexer_controlwith actionstatusand the project'srepo_id. Always pass therepo_id: that call is slow without one. - If the health result shows the user is not signed in, ask them to run
synapse-mcp authin a terminal. - If the Synapse tools are not available, ask the user to run
synapse-mcp statusin a terminal and tell you what it prints.- Command not found: Synapse is not installed. Point the user to https://synapse-mcp.dev/download. Do not download or run an installer yourself.
- Installed but stopped: suggest
/synapse-mcp:start. - Running, but the tools are still missing: the plugin's Synapse URL may not match. The default is
http://127.0.0.1:8585/mcp. Ask the user to check it under/plugin, then reconnect the server from/mcp.
Keep the report short. Do not list every tool or repository unless the user asks.
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 · 19 lines · 58 tokens per session scan A 55bdedcdf38a
status is a skill published in the GitHub repository myelixlabs/synapse-mcp (3 stars, last pushed 6d ago), licensed MIT. It adds 58 tokens to every session and 433 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-codemod
Use trace-mcp applycodemod for any bulk mechanical change instead of repeated Edit calls. Activate whenever the same edit pattern would be applied 2+ times, across one file or many.
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.
trace-mcp-pre-commit
Run trace-mcp security, quality-gate, and antipattern checks before committing or opening a PR. Activate when the agent is about to create a commit or pull request in a project indexed by trace-mcp.
trueline-workflow
Use when editing, reading, searching, or exploring files with trueline MCP tools (truelineread, truelineedit, truelinesearch, truelineoutline, truelineverify, truelinechanges). Covers when to pick trueline over built-in Read/Edit/Grep, ref reuse, hash-verified edits, search-then-edit, insertafter semantics, workflows…
analyze-usage
Use when asked to analyze codescout tool usage, check for error patterns, audit tool health, generate a usage report, spot anti-patterns, or clear usage statistics to start fresh.