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/procoders/superpowers-vWrote 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/procoders/superpowers-v/marketplace)<a href="https://agentmods.dev/plugins/procoders/superpowers-v/marketplace"><img src="https://agentmods.dev/badge/plugins/procoders/superpowers-v/marketplace/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/procoders/superpowers-v/marketplace"><img src="https://agentmods.dev/badge/plugins/procoders/superpowers-v/marketplace.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
procoders marketplace 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 6d 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": "procoders",
"description": "procoders plugins marketplace",
"owner": {
"name": "Oleg",
"email": "[email protected]"
},
"plugins": [
{
"name": "compound-v",
"description": "Senior-engineer habits for Claude Code: a one-question-at-a-time brainstorm, one builder that researches, plans and codes (with a DESIGN.md design pass for UIs), then verification with tests, a real browser, an independent reviewer and a scope check, each a signed receipt bound to the working tree.",
"source": "./"
},
{
"name": "superpowers-v",
"description": "Compound V 3.x (legacy orchestrator), kept on the v3 branch for existing users.",
"source": {
"source": "github",
"repo": "procoders/superpowers-v",
"ref": "v3"
}
}
]
}
The plugins it lists here
This marketplace lists 1 plugin kept in the same repository. Each has its own page, its own measurements and its own install command.
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.
- 6d ago Changed · +4 lines d200be79ddbf
- 1mo ago First seen · 21 lines scan A d526faa79428
procoders marketplace is a plugin published in the GitHub repository procoders/superpowers-v (42 stars, last pushed today), 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
beads-superpowers
Superpowers skills + Beads issue tracking for Claude Code, Codex, OpenCode, and 7 more AI coding agents. Composable skills + persistent task memory.
beads-superpowers
Superpowers skills + Beads issue tracking for Gemini CLI. Composable skills + persistent task memory.
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 two opt-in hooks: leg-guard…
good-bad-ugly
The Good, the Bad and the Ugly — tiered multi-agent orchestration for Claude Code. The Good (brain) plans and verifies, the Bad (judgment executor) handles work needing taste, the Ugly (mechanical executor) does the grunt work — in parallel herdr panes with fenced scopes.
fabulous
Fable 5 behaviour for Opus-family models: doctrine injected at session start plus per-task reference playbooks.
superpowers-cc-to-codex
Codex-backed fork of seven Superpowers workflows: brainstorming, planning, implementation, code review, debugging, TDD, and branch completion.