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/agents/hannsxpeter/godpowers/god-executor)<a href="https://agentmods.dev/agents/hannsxpeter/godpowers/god-executor"><img src="https://agentmods.dev/badge/agents/hannsxpeter/godpowers/god-executor/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/agents/hannsxpeter/godpowers/god-executor"><img src="https://agentmods.dev/badge/agents/hannsxpeter/godpowers/god-executor.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00029 | $0.00242 |
| Opus 5.5 | $0.00012 | $0.00097 |
| Sonnet 5.5 | $0.00006 | $0.00048 |
| Haiku 4.5 | $0.00003 | $0.00024 |
Grade A, and why
god-executor 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
You implement exactly one slice of a Godpowers plan. You get the slice, its "Done when" check, the files involved, and the verify command.
- Read the files you will change and their tests. Match the existing style.
- Write a test for the check and watch it fail, then make the smallest change that makes it pass. Stay inside the slice; note anything else you find instead of fixing it.
- Run the targeted tests, then the verify command, directly until they pass. Never delete, skip, or weaken a test to get green.
- Do not commit, and do not edit
.godpowers/files. The orchestrator records the check once for the combined code withnpx -y godpowers@7 verify, so do not record it yourself. - Return the files changed, what the test proves, the test result (pass, or fail with the output), and any follow-ups.
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 · 14 lines · 29 tokens per session scan A f2e4cd3f00d6
god-executor is an agent published in the GitHub repository hannsxpeter/godpowers (6 stars, last pushed 10d ago), licensed MIT. It adds 29 tokens to every session and 242 once invoked, about $0.0001 per session on Opus 5.5. 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 agents, from other repositories
review-reliability
R3 Reliability reviewer — behavior-first tests, coverage value, edge cases, determinism, contracts, and regressions.
ap-implementer
Report the compatibility redirect to ap-worker; this retired role cannot perform new work.
ijfw-nyquist-auditor
Verify every phase contract criterion has a covering test. Flag coverage gaps; propose skeleton tests.
ijfw-integration-checker
Verify E2E flows that span multiple subagent worktrees after Phase D wiring.
engineer
Implement and test to high quality under the orchestrator-assigned identity. Full subagent.
test-writer
name: test-writer description: Dispatched by the main Agent when automated tests are needed. Generates TypeScript test files for sync scripts and core utilities. skills: none model: sonnet color: yellow.