Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add SyloRei/claude-godmode/plugin install claude-godmodeWrote 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/sylorei/claude-godmode/ship)<a href="https://agentmods.dev/skills/sylorei/claude-godmode/ship"><img src="https://agentmods.dev/badge/skills/sylorei/claude-godmode/ship.svg" alt="Measured on agentmods" 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.00043 | $0.04981 |
| Opus 5 | $0.00022 | $0.02491 |
| Sonnet 5 | $0.00009 | $0.00996 |
| Haiku 4.5 | $0.00004 | $0.00498 |
Grade B, and why
ship scanned grade B with 1 finding 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 8d 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
Don't re-derive the gate-running loop: invoke the bundled **`skills/ship/scripts/gates.sh`**. It resolves `config/quality-gates.txt` across install modes (`${CLAUDE_PLUGIN_ROOT}/config` → `~/.claude/config` → repo-relati How it starts
The opening of the file, as written. The whole thing — 281 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ship
Take a verified work unit to a pull request: run the canonical quality gates, then — only if every gate passes — push the branch and open a PR. This is the final step of the spine: /mission → /brief N → /plan N → /build N → /verify N → /ship.
/ship is side-effecting (it pushes and opens a PR), so it is user-triggered only (disable-model-invocation: true). It is never auto-invoked.
Flags
--no-push(aliases:--dry-run,--local) — run every quality gate and the findings gate (Step 1b), prepare git readiness (commit), then stop before the push and the PR. Draft and print the PR title/body for review, but do not rungit pushorgh pr create, and do not recordstatus=shipped. Use this to land a verified, committed, gate-green branch locally without publishing it.--no-pushdoes not exempt the findings gate any more than it exempts the quality gates: open blocking findings BLOCK--no-pushtoo (no commit), exactly as they BLOCK a normal ship.
When --no-push is set the confirmation prompt is moot — there is nothing side-effecting to confirm — so skip it and run the gates and git readiness straight through.
Confirm by default
/ship confirms with the user before the side-effecting steps (the push and the gh pr create). This confirm follows the shared convention in rules/godmode-recommend.md (godmode:recommend-convention) — its confirm/proceed rendering: lead with a Recommended: proceed line carrying a visible one-line rationale, then let the user override.
After the gates pass and the PR body is drafted, show the branch, target, and PR title/body, then lead with the recommended-proceed confirm before pushing — for example:
Recommended: proceed — every quality gate and the findings gate are green, and
the PR body is drafted. Reply "go" to push and open the PR, or name what to change.
Wait for explicit confirmation before pushing.
Exception — Auto Mode. When ## Auto Mode Active is present in context, skip the confirmation prompt: proceed straight to push and PR create on the default choices, and treat any user course-correction as normal input. The quality-gate block (Step 1) and the findings gate (Step 1b) are never skipped, in either mode — Auto Mode skips only the confirmation, never a BLOCK. (The findings gate's waive escape is inherently conversational, so it still requires an explicit user-named ID + reason even under Auto Mode; Auto Mode never auto-waives.)
What ships with it
1 file beside SKILL.md 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.
- 8d ago First seen · 281 lines · 43 tokens per session scan B 99b01922a6e5
ship is a skill published in the GitHub repository SyloRei/claude-godmode (3 stars, last pushed 3mo ago), licensed MIT. It adds 43 tokens to every session and 4,981 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
ship-pipeline
Run when all code changes are complete and ready to land. Executes the full merge+test+commit+push+PR pipeline. Do not run mid-feature.
release
Use when cutting a versioned release. Detects commits since last tag, suggests semver bump, bumps version file, tags, pushes, and creates a GitHub release. Distinct from ship-pipeline which ends with a PR.
release
Bump a plugin's version, write a detailed changelog entry for the upgrade skill to consume, and commit+push. Takes a plugin slug argument identifying which plugin under plugins/ to release. Use this skill whenever the user says "release", "version bump", "cut a release", "changelog and push", or finishes a set of…
pre-release-review
Run the pre-release gate for this multi-plugin monorepo: establish each plugin's release boundary from its last reachable tag to HEAD, audit every changed plugin's [Unreleased] changelog against the actual code diff, identify contract-surface and breaking changes, and, per the objective the user picks up front, either…
fleet-release
Use this skill whenever the user wants to release, ship, prep, or cut versions for two or more plugins together on the current branch. Trigger on phrasings like "release both plugins", "ship them together", "release all changed plugins", "fleet release", "multi-plugin release", "release in order", or "release…
pipeline-digest
Daily release-pipeline digest with a change gate — reports which plugins are pending release, whether main's CI is green, and which branches went stale, and notifies the operator only when that state actually moved since the last run. Use when the operator asks "what moved in the pipeline", "anything to ship"…