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-shipgit 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-ship)<a href="https://agentmods.dev/skills/hannsxpeter/godpowers/god-ship"><img src="https://agentmods.dev/badge/skills/hannsxpeter/godpowers/god-ship/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-ship"><img src="https://agentmods.dev/badge/skills/hannsxpeter/godpowers/god-ship.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.00306 |
| Opus 5.5 | $0.00023 | $0.00122 |
| Sonnet 5.5 | $0.00011 | $0.00061 |
| Haiku 4.5 | $0.00006 | $0.00031 |
Grade A, and why
god-ship 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-ship
- Run
npx -y godpowers@7 gate ship. Fix every failed check before going further. Never record a pass you did not earn. - Make sure the release path fits the project, and add what is missing:
- Build and deploy are repeatable from a clean checkout, and the tested artifact is the one released.
- Rollback is written down and has been tried once.
- A health check exercises a real dependency, not just an open port.
- Errors are captured, and one or two signals tied to the goal are visible (for example, sign-up success rate).
- Release notes or a changelog entry, in the project's style.
- Publishing, production deploys, tags, and announcements are public or irreversible. Ask before each one unless the user already asked for it in this session.
- After shipping, run the health check against the live target and record it:
npx -y godpowers@7 record ship --pass --summary "<version, where, health result>". - Set
stage: done(orplanfor the next goal) and summarize what shipped.
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 · 18 lines · 57 tokens per session scan A dd350b24b293
god-ship 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 306 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
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-preflight
Run the IJFW preflight pipeline (11 gates, fail-fast). Trigger: 'ijfw preflight', 'run preflight', 'check before ship', 'preflight gates', 'validate before release'.
release-verification
A release-verification checklist for software versions and packages. It covers changelogs, tests, packaging, installation smoke checks, version-control actions, publishing, and checks after release.
audit-release
A pre-release review assistant that checks whether a software package or plugin is ready to publish.
gentle-ai-collab-perfect
Trigger: contributing to Gentleman-Programming/gentle-ai as an external collaborator. Strict issue-first workflow, honest PR bodies, contributor-vs-maintainer scope, chained-PR strategy, verification protocol, docstring coverage. Load whenever the active repo is Gentleman-Programming/gentle-ai and any part of the…
branch-pr
Create Gentle AI pull requests with issue-first checks. Trigger: creating, opening, or preparing PRs for review.