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/hannsxpeter/godpowersWrote 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/hannsxpeter/godpowers/godpowers)<a href="https://agentmods.dev/plugins/hannsxpeter/godpowers/godpowers"><img src="https://agentmods.dev/badge/plugins/hannsxpeter/godpowers/godpowers/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/hannsxpeter/godpowers/godpowers"><img src="https://agentmods.dev/badge/plugins/hannsxpeter/godpowers/godpowers.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
godpowers 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 11d 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": "godpowers",
"version": "7.0.0",
"description": "Durable project state, evidence-backed \"done\", and gates enforced by hooks. Eight commands and four agents.",
"author": {
"name": "Godpowers"
},
"homepage": "https://github.com/hannsxpeter/godpowers#readme",
"repository": "https://github.com/hannsxpeter/godpowers",
"license": "MIT",
"keywords": ["verification", "hooks", "state", "review", "security"]
}
What it installs
The manifest is a name and a version. 9 skills, 4 agents, 3 hooks travel with it, and installing the plugin installs all of them — 558 tokens a session between them. Each is measured on its own page, and each can be installed alone.
- Skill godpowers A 0 tokens
- Skill god-review A 52 tokens
- Skill god A 47 tokens
- Skill god-build A 50 tokens
- Skill god-harden A 53 tokens
- Skill god-plan A 56 tokens
- Skill god-ship A 57 tokens
- Skill god-init A 57 tokens
- Skill god-status A 36 tokens
- Agent god-reviewer A 40 tokens
- Agent god-security-auditor A 45 tokens
- Agent god-executor A 29 tokens
- Agent god-planner A 36 tokens
- Hook PreToolUse A not measured
- Hook SessionStart A not measured
- Hook Stop A not measured
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.
- 11d ago First seen · 13 lines scan A 86f09277457e
godpowers is a plugin published in the GitHub repository hannsxpeter/godpowers (6 stars, last pushed 10d 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-09-27.
Other plugins, from other repositories
ijfw
IJFW -- AI efficiency layer for Gemini CLI. 19 workflow skills, 11-event hooks, persistent project memory via MCP. Native policy engine + checkpointing integration. One install layer across 15 AI coding platforms.
ring-pm-team
Pre-dev planning workflows: 4-gate and 8-gate orchestrators for PRD, TRD, OpenAPI contracts, schema design, and a phased plan. 14 skills + 4 research agents.
papi
Persistent project management inside your AI coding tool. PAPI plans what to build next, tracks every decision, and keeps projects coherent across sessions — so a new session starts where the last one left off instead of from nothing.
shipwithai-starter
Sets up a standardized Claude Code harness for your project: CLAUDE.md, permissions, hooks, MCP servers, agents, SSOT docs, and observability logging. One init interview, consistent harness across every team member.
essentials
24 commands, 8 agents. Loops, swarms, and teams powered by Claude Code's built-in Task System. Native task dependencies, ctrl+t progress, automatic persistence.
humanizer
Rewrite AI-sounding text so it reads like the writer without changing what it says.