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 ushibo/brigadenpx agentmods add plugins/ushibo/brigade/marketplacegit clone --depth 1 https://github.com/ushibo/brigadeGrade A, and why
ushibo 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- brigade — 86% identical, 47 lines differ
What it actually says
{
"name": "ushibo",
"description": "ushibo marketplace — Claude Code plugins by ushibo",
"owner": {
"name": "ushibo",
"email": "[email protected]",
"url": "https://github.com/ushibo"
},
"plugins": [
{
"name": "brigade",
"description": "Your AI dev brigade for Claude Code. A chef (sprint planner) coordinates specialist agents (frontend, designer, nodejs, golang, devops) through wave-based execution with fan-out review, Bug Council for hard bugs, and sprint learnings between iterations. Zero dependencies.",
"version": "1.8.2",
"source": "./",
"category": "development",
"author": {
"name": "Sergey Akhantev",
"email": "[email protected]",
"url": "https://github.com/ushibo"
},
"homepage": "https://github.com/ushibo/brigade",
"repository": "https://github.com/ushibo/brigade",
"license": "MIT",
"keywords": [
"claude-code",
"multi-agent",
"sprint",
"code-review",
"ai-development",
"fullstack",
"worktree",
"bug-council"
]
}
]
}
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 · 37 lines scan A 19322ed6da9d
ushibo is a plugin published in the GitHub repository ushibo/brigade (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
rube-cc-skills
A curated collection of Claude Code plugins.
ci-review
CI-optimized code review: multi-agent parallel review with confidence scoring and atomic GitHub PR review posting via gh api.
rpm
Relentless Project Manager. Prevents drift and keeps you on task across LLM-assisted development sessions.
radin
Cost-optimized agentic workflow stack for solo devs: backlog orchestration (radin-orchestrator, radin-plan, radin-review) plus curated companion tools.
agent-taskgraph
PMO-led native Claude Code Agent Teams with isolated contexts and document handoffs.
dev-day
The complete developer day-loop for Claude Code + Jira: /start-session boots a senior-collaborator session (feedback memory, Jira backlog, standing plan-gate), /standup answers 'anything pending?', /bug-triage root-causes tickets, /groom preps them for estimation, /create-ticket files them, /jira-comment posts clean…