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 serdardb/multi-agentnpx agentmods add plugins/serdardb/multi-agent/plugingit clone --depth 1 https://github.com/serdardb/multi-agentGrade A, and why
multi-agent 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
{
"name": "multi-agent",
"version": "0.1.2",
"description": "Run your OWN agent on other AI model CLIs (grok / codex / claude) as independent second opinions — no API, each model runs the agent natively. Two commands: /multi-agent (a single-model, live, steerable review you can talk to while it runs) and /arena (a deterministic multi-model adversarial arena — independent audit → cross-critique until positions converge → code-verifying judge → scoreboard, shown live in /workflows).",
"author": { "name": "Serdar Doğrubakar", "url": "https://github.com/serdardb" },
"homepage": "https://github.com/serdardb/multi-agent",
"repository": "https://github.com/serdardb/multi-agent",
"license": "MIT",
"keywords": ["code-review", "multi-model", "cross-model", "arena", "adversarial", "second-opinion", "security", "claude-code", "grok", "codex", "workflow"]
}
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 · 11 lines scan A dd40abcd973a
multi-agent is a plugin published in the GitHub repository serdardb/multi-agent (1 stars, last pushed 1mo 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-31.
Other plugins, from other repositories
code-gauntlet
Plugin marketplace listing 1 plugin: code-gauntlet.
skillet
A skillet full of agent skills for repo audits, publish gates, execution discipline, memory handoffs, and decision-ready briefs.
audit-protocol
Audits a code change against a 54-phase failure taxonomy and reports what it did not check, not just what it found. Domain overlays run first and force critical-path treatment.
taxcraft
US tax and accounting work for people whose situation outgrew consumer software but who still do the prep themselves: multiple entities, K-1s that arrive late and wrong, basis and carryforwards nobody is tracking, quarterly estimates guessed at rather than computed. It builds the workpapers a CPA would build …
rn-agents-kit
Audit-first agent skills for React Native maintenance.
rn-agents-kit
Audit-first agent skills for React Native maintenance: code-quality audit, New Architecture readiness, asset hygiene, project snapshot, device screen capture, and Metro console capture.