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/barkain/madroxWrote 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/barkain/madrox/madrox)<a href="https://agentmods.dev/plugins/barkain/madrox/madrox"><img src="https://agentmods.dev/badge/plugins/barkain/madrox/madrox/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/barkain/madrox/madrox"><img src="https://agentmods.dev/badge/plugins/barkain/madrox/madrox.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
madrox 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 1mo 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": "madrox",
"version": "1.9.1",
"description": "MCP server that orchestrates multiple Claude CLI instances as parallel workers with a real-time dashboard",
"author": {
"name": "Nadav Barkai"
},
"repository": "https://github.com/barkain/madrox",
"license": "MIT",
"keywords": ["mcp", "orchestration", "multi-agent", "parallel", "dashboard"]
}
What it installs
The manifest is a name and a version. 1 skill, 1 MCP server travel with it, and installing the plugin installs all of them — 11 tokens a session between them. Each is measured on its own page, and each can be installed alone.
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.
- 1mo ago First seen · 12 lines scan A a5087f77fac1
madrox is a plugin published in the GitHub repository barkain/madrox (5 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-31.
Other plugins, from other repositories
pilotfish
macOS and Linux Claude Code Plugin with hook-based ambient policy activation and namespaced role agents.
relay
Delegate work packets from a lead Claude Code session to executor sessions in their own iTerm tabs, with session reuse instead of always spawning fresh.
agentos
Agent Operating System — self-evolving agents, multi-agent orchestration, 25-screen TUI, 25 LLM providers. Built on iii-engine.
agent-taskgraph
Build native Claude Code Agent Teams with goals, roles, task graphs, collaboration protocols, and lifecycles.
ac
Main-agent planning trio (/ac:plan, /ac:execute, /ac:wisdom) with autonomous execution mode plus setup, init, commit commands and skill, agent, command, rule, CLAUDE.md creator skills. Two hooks back the workflow: SessionStart for twin-skill and resume, PreCompact for state preservation.
git-master
Git expert skill — atomic commits, interactive rebase, and history archaeology for Claude Code.