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 barkain/claude-code-workflow-orchestrationnpx agentmods add plugins/barkain/claude-code-workflow-orchestration/marketplacegit clone --depth 1 https://github.com/barkain/claude-code-workflow-orchestrationGrade A, and why
barkain-plugins 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 2d 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": "barkain-plugins",
"owner": {
"name": "Nadav Barkai"
},
"plugins": [
{
"name": "workflow-orchestrator",
"source": "./",
"description": "Delegation system with workflow orchestration, specialized agents, and parallel execution for Claude Code",
"version": "2.1.1",
"author": {
"name": "Nadav Barkai"
},
"repository": "https://github.com/barkain/claude-code-workflow-orchestration",
"license": "MIT",
"keywords": ["delegation", "workflow", "orchestration", "agents"],
"category": "productivity"
},
{
"name": "madrox",
"description": "MCP server that orchestrates multiple Claude CLI instances as parallel workers with a real-time dashboard",
"version": "1.9.1",
"source": {
"source": "github",
"repo": "barkain/madrox"
},
"category": "productivity",
"homepage": "https://github.com/barkain/madrox"
}
]
}
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.
- 2d ago First seen · 33 lines scan A 98cea87a8377
barkain-plugins is a plugin published in the GitHub repository barkain/claude-code-workflow-orchestration (84 stars, last pushed 29d 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
claude-workflow
Unified spec-to-execution workflow system. Combines spec rigor, autonomous execution, and native task orchestration with parallel agent dispatch. Swarms-ready architecture.
claude-workflow
Plugin marketplace listing 1 plugin: claude-workflow.
humanizer
Rewrite AI-sounding text so it reads naturally without changing what it says.
nextjs
Official Next.js skills: adopt and optimize Cache Components, adopt Partial Prefetching, and verify runtime behavior against a running dev server.
nextjs
Official Claude Code plugin marketplace for Next.js, serving the skills that ship in the vercel/next.js repository.
claude-plugins-official
Directory of popular Claude Code extensions including development tools, productivity plugins, and MCP integrations.