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.
/plugin marketplace add msanchezdev/agent-bridgenpx agentmods add plugins/msanchezdev/agent-bridge/marketplacegit clone --depth 1 https://github.com/msanchezdev/agent-bridgeGrade A, and why
agent-bridge 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 yesterday.
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
{
"$schema": "https://json.schemastore.org/claude-code-marketplace.json",
"name": "agent-bridge",
"owner": {
"name": "Manuel Sanchez",
"email": "[email protected]",
"url": "https://github.com/msanchezdev"
},
"metadata": {
"description": "File-based chat for Claude Code instances — group channels and DMs, namespaced per project."
},
"plugins": [
{
"name": "agent-bridge",
"source": "./",
"description": "Join a per-project group chat shared by Claude Code instances (group channels + DMs) and watch for messages from other Claude instances.",
"version": "1.1.1",
"author": {
"name": "Manuel Sanchez",
"email": "[email protected]"
},
"homepage": "https://github.com/msanchezdev/agent-bridge",
"keywords": ["chat", "multi-agent", "collaboration", "messaging", "dm"]
}
]
}
What ships with it
1 file beside marketplace.json 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.
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.
- yesterday First seen · 27 lines scan A e2a42b3e5f63
agent-bridge is a plugin published in the GitHub repository msanchezdev/agent-bridge (20 stars, last pushed 2mo ago), 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-08-30.
Other plugins, from other repositories
bjgreenberg
Claude Code plugins by Brian Greenberg.
senior-engineering-partner
A strict code reviewer, pair programmer, debugger, and mentor for Python, Bash, Google Apps Script, and JavaScript — a security-first, phase-aware engineering discipline with an enforced spec → plan → TDD → verify workflow.
vanguard-frontier-agentic
Cloud and zero-trust agentic workflow marketplace for skills, agents, rules, MCP references, and compliance-aware architecture.
vanguard-frontier-agentic
Plugin marketplace listing 1 plugin: vanguard-frontier-agentic.
wan-huiyan-agent-traffic-control
Coordination toolkit for parallel Claude Code sessions sharing one repo — issue-pickup claim protocol (assignee + wip label), worktree & session-isolation pitfalls, parallel-PR conflict recovery, subagent-integrity edge cases, and squash/merge mechanics for parallel-PR workflows.
agent-traffic-control
Coordination toolkit for parallel Claude Code sessions sharing one repo — issue-pickup claim protocol (assignee + wip label), worktree & session-isolation pitfalls, parallel-PR conflict recovery, subagent-integrity edge cases, and squash/merge mechanics for parallel-PR workflows. Plus resume-gate, an opt-in hook that…