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.
git clone --depth 1 https://github.com/mpesavento/swarmbusWrote 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/plugins/mpesavento/swarmbus/marketplace)<a href="https://agentmods.dev/plugins/mpesavento/swarmbus/marketplace"><img src="https://agentmods.dev/badge/plugins/mpesavento/swarmbus/marketplace/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/plugins/mpesavento/swarmbus/marketplace"><img src="https://agentmods.dev/badge/plugins/mpesavento/swarmbus/marketplace.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
swarmbus marketplace 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 5d 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
{
"name": "swarmbus",
"description": "swarmbus plugins for Claude Code: peer messaging between AI agents over MQTT",
"owner": {
"name": "Mike Pesavento",
"url": "https://github.com/mpesavento"
},
"plugins": [
{
"name": "swarmbus",
"source": {
"source": "git-subdir",
"url": "https://github.com/mpesavento/swarmbus.git",
"path": "plugins/swarmbus",
"ref": "main"
},
"description": "Message other agents over swarmbus: the MCP sidecar (send_message, read_inbox, agent_state) and the using-swarmbus skill"
}
]
}
The plugins it lists here
This marketplace lists 1 plugin kept in the same repository. Each has its own page, its own measurements and its own install command.
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.
- 5d ago Changed fdad18d3b9c8
- 9d ago First seen · 21 lines scan A ff84e48f4499
swarmbus marketplace is a plugin published in the GitHub repository mpesavento/swarmbus (13 stars, last pushed today), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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-11-01.
swarmbus marketplace compared with plugins from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| swarmbus marketplacempesavento/swarmbus | Plugin | 13 | today | MIT | A | — | Claude Code |
| jkavivsinai/jenkins-cli | Plugin | 98 | today | MIT | A | — | Claude Code |
| harness-platformharness/harness-skills | Plugin | 133 | 13d ago | Apache-2.0 | A | — | Claude Code |
| jira-packatretyak1985/swarmery | Plugin | 7 | yesterday | Apache-2.0 | A | — | Claude Code |
| misticosIvMisticos/misticos.Claude | Plugin | 3 | 2d ago | MIT | A | — | Gemini CLI |
| claude-superskills marketplaceericgandrade/claude-superskills | Plugin | 88 | 6mo ago | MIT | A | — | Claude Code |
| collateMidnightDarling/collate | Plugin | 8 | 5mo ago | Apache-2.0 | A | — | Claude Code |