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.
npx skills add hannsxpeter/godpowers --skill god-initgit 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/skills/hannsxpeter/godpowers/god-init)<a href="https://agentmods.dev/skills/hannsxpeter/godpowers/god-init"><img src="https://agentmods.dev/badge/skills/hannsxpeter/godpowers/god-init/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/skills/hannsxpeter/godpowers/god-init"><img src="https://agentmods.dev/badge/skills/hannsxpeter/godpowers/god-init.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.00057 | $0.00311 |
| Opus 5.5 | $0.00023 | $0.00124 |
| Sonnet 5.5 | $0.00011 | $0.00062 |
| Haiku 4.5 | $0.00006 | $0.00031 |
Grade A, and why
god-init 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
/god-init
- Run
npx -y godpowers@7 status.- If it reports the 6.x layout: run
npx -y godpowers@7 migrate --dry-run, show the user what will move, then runnpx -y godpowers@7 migrate. It archives the old files under.godpowers/archive/and removes the old instruction blocks from AGENTS.md, CLAUDE.md, and editor rule files. - If the project is already set up: say so and stop.
- If it reports the 6.x layout: run
- Otherwise run
npx -y godpowers@7 init. Add--verify "<command>"when the check command is not detected, and--no-agents-mdif the user does not want the short note in AGENTS.md. - Fill in STATE.md: the Goal (one or two sentences, in the user's words) and Next. Ask one question only if you cannot infer the goal.
- Run
npx -y godpowers@7 verifyonce to prove the check command works, thennpx -y godpowers@7 doctorto confirm the hooks are registered. Report anything missing with its fix.
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 · 57 tokens per session scan A 541d9becd3f6
god-init is a skill published in the GitHub repository hannsxpeter/godpowers (6 stars, last pushed 10d ago), licensed MIT. It adds 57 tokens to every session and 311 once invoked, about $0.0002 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 skills, from other repositories
issue-creation
Trigger: issue creation, bug reports, feature requests, or issue approval. Create and triage GitHub issues from repository evidence.
systemic-issue-triage
Trigger: new issue, bug report, triage, backlog, issue flood, community report, root cause, dead-end, blocked user. Attack issues by root class, never one-by-one; fixes must shrink the system, not grow it.
ijfw-workflow
Use when the user says: 'build', 'create', 'plan', 'new project', 'brainstorm', 'design', 'UI', 'website', 'dashboard', 'app', 'help me build', 'launch', 'book', 'campaign', or anything project-level. Skill body decides Quick vs Deep path.
ijfw-plan
Use when the user says 'plan this', 'plan it', 'make a plan', 'let's plan', 'draft a plan', 'how should we tackle this', 'break this down', or invokes '/ijfw-plan'. Produces a falsifiable PLAN.md (software, book, campaign, design, research) with task breakdown, dependency wave-table, and success criteria — gated by…
ijfw-ship
Use when the user says 'ship it', 'ship this', 'release', 'publish', 'launch', 'deploy', 'go live', 'wrap this up', 'time to ship', or invokes '/ijfw-ship'. Domain-aware release — software (test → tag → push → publish), book (final edit → format → KDP / agent / Substack), campaign (review → schedule → launch →…
ijfw-complete-milestone
Use when a milestone is shipping and you need to archive its artifacts, generate a summary, and seed the next milestone. Trigger: 'milestone complete', 'ship milestone', 'wrap milestone', 'complete milestone ', /ijfw-complete-milestone.