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/7xuanlu/ultrapowersWrote 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/7xuanlu/ultrapowers/ultrapowers)<a href="https://agentmods.dev/plugins/7xuanlu/ultrapowers/ultrapowers"><img src="https://agentmods.dev/badge/plugins/7xuanlu/ultrapowers/ultrapowers/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/7xuanlu/ultrapowers/ultrapowers"><img src="https://agentmods.dev/badge/plugins/7xuanlu/ultrapowers/ultrapowers.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
ultrapowers 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.
This is a copy
88% identical to 7xuanlu marketplace — 28 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
{
"name": "ultrapowers",
"version": "0.4.3",
"description": "A dynamic build workflow for Claude Code: hand it a goal and it plans the work into tasks, builds each one test-first, reviews every step, and (with --thorough) loops a critic that adds tasks until nothing's left to fix, then hands back a branch ready for your review. Built on and complements superpowers by Jesse Vincent (@obra); does not replace it.",
"author": {
"name": "Qi-Xuan Lu (@7xuanlu)"
},
"license": "MIT"
}
What it installs
The manifest is a name and a version. 1 skill, 1 agent, 2 hooks travel with it, and installing the plugin installs all of them — 105 tokens a session between them. Each is measured on its own page, and each can be installed alone.
What ships with it
1 file beside plugin.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.
- 1mo ago First seen · 10 lines scan A b6d6ea1d675d
ultrapowers is a plugin published in the GitHub repository 7xuanlu/ultrapowers (10 stars, last pushed 3mo 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. It is 88% identical to 7xuanlu marketplace, differing in 28 lines, and is treated as a copy.
Other plugins, from other repositories
superpowers-cc-to-codex
Codex-backed fork of seven Superpowers workflows: brainstorming, planning, implementation, code review, debugging, TDD, and branch completion.
atdd
Acceptance Test Driven Development for Claude Code. Enforces the ATDD methodology: write Given/When/Then specs first, generate a project-specific test pipeline, maintain two test streams (acceptance + unit). Inspired by Robert C. Martin's acceptance test approach from empire-2025.
hcf
Autonomous development orchestration with parallel TDD execution.
dev-loop
Multi-agent orchestration grounded in an LLM wiki. /dev-loop:orchestrate splits one goal into a dependency graph of parallel Claude Code sessions, each in its own worktree, and supervises them natively on Orca (a tracked Task + Dispatch per phase, pushed workerdone / question / escalation events instead of polling, st.
quality-gates marketplace
Quality-gate plugins for Claude Code: manifest-driven audit/fix pipelines with enforced plan-first, secret-safety and TDD discipline.
flow
Skill-driven workflow plugin for GitHub development with excellence-by-default quality gates. Encodes team knowledge as composable skills, enforces safety through hooks, and compounds learning across sessions. Strict TDD, Stranger Test, holdout validation, and evidence-based verification built in. Durable goals…