agentmods.dev

ship

ship is a skill for Claude Code, Codex from kreek/consult. It costs 22 tokens per session (763 once invoked), scanned A, original, MIT.

A guarded release workflow for the Consult repository. It covers committing, merging, version changes, validation, and pushing code, with a confirmation pause at each gate.

In plain words
What is it for?
Use it when releasing Consult, including checking the repository, preparing release commits, updating the appropriate version files, validating the result, and pushing it.
Why use it?
It reduces the risk of publishing the wrong changes or changing the two independent release versions incorrectly.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: mentions .claude-plugin; installed under .agents/ (shared by several agents); mentions Codex.

not rated 1repo 20d ago A scan 22 tokens original MIT

Good fit Use it when releasing Consult, including checking the repository, preparing release commits, updating the appropriate version files, validating the result, and pushing it.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/kreek/consult/ship
View source ↗ kreek/consult
Install

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.

Any agent
npx skills add kreek/consult --skill ship
Clone the repo
git clone --depth 1 https://github.com/kreek/consult

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for ship

README.md
[![agentmods](https://agentmods.dev/badge/skills/kreek/consult/ship/github.svg)](https://agentmods.dev/skills/kreek/consult/ship)
Your own site
<a href="https://agentmods.dev/skills/kreek/consult/ship"><img src="https://agentmods.dev/badge/skills/kreek/consult/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.

agentmods 80×15 button for ship

Your own site · 80×15
<a href="https://agentmods.dev/skills/kreek/consult/ship"><img src="https://agentmods.dev/badge/skills/kreek/consult/ship.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 22 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 763 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00022 $0.00763
Opus 5.5 $0.00009 $0.00305
Sonnet 5.5 $0.00004 $0.00153
Haiku 4.5 $0.00002 $0.00076

Measured 1mo ago against content hash 9297e897150e, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

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 1mo 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.

.agents/skills/ship/SKILL.md · 74 lines

How it starts

The opening of the file, as written. The whole thing — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Ship

When to Use

  • Use when the user asks to ship this Consult repository or explicitly invokes $ship.
  • Use only for this repository's maintainer release flow: commit, merge to main, bump release artifacts, validate, and push.

When NOT to Use

  • Do not use for ordinary commits; use the commit skill instead.
  • Do not use for release preparation by itself; use the release skill.
  • Do not use outside this repository.

Iron Law

DO NOT RUN THE WHOLE SHIP FLOW UNATTENDED; STOP AT EVERY CONFIRMATION GATE.

Repo Facts

  • Main branch is main; remote is origin.
  • There are two independent release streams. Never bump them in lockstep.
  • Plugin version lives in plugin/.claude-plugin/plugin.json, plugin/.codex-plugin/plugin.json, plugin/.cursor-plugin/plugin.json, .claude-plugin/marketplace.json, and .cursor-plugin/marketplace.json. plugin/plugin.json should match these too; reconcile drift when bumping.
  • The consult npm package version lives in consult/package.json. Bump it only when the diff changes the published package.
  • Root package.json is private tooling and is not versioned for release.
  • Version marker is the CHANGELOG.md header ## [X.Y.Z] (YYYY-MM-DD). Promote ## [Unreleased] into a dated version section and leave a fresh empty ## [Unreleased] above it.
  • Releases are not git-tagged in this repo. Do not create or push a tag unless the user explicitly asks.
  • Commit messages use imperative subjects and no author-attribution trailers.

Workflow

  1. Pre-flight: run git status and git rev-parse --abbrev-ref HEAD. If the working tree is clean and already on main, report that there is nothing to ship and stop.
  2. Commit: review git diff and git diff --cached, group uncommitted changes into logical commits, propose the grouping, and get user approval before committing on the current branch.
  3. Merge to main, only when not already on main: run git fetch origin, bring main up to date, get user approval, then merge the current branch into main. On conflicts, stop and show the conflicted files.
  4. Bump the version on main: use the release skill to classify the bump from the merged diff, or use the user's explicit patch, minor, or major override. Confirm the proposed version before writing. Update the relevant release artifacts and commit the bump as Release <version>.
  5. Validate and push: run the project validation gate before pushing. Abort on failure. Get user approval before git push origin main.

Read the full file on GitHub · 74 lines

Changes

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.

  1. 1mo ago First seen · 74 lines · 22 tokens per session scan A 9297e897150e

Subscribe to this mod's changes

ship is a skill published in the GitHub repository kreek/consult (1 stars, last pushed 20d ago), licensed MIT. It adds 22 tokens to every session and 763 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-08-31.

Claude CodeGit and workflowReleasesagenticai-agentsclaude-code-pluginclaude-skillscodex-plugin
Related

Other skills, from other repositories

deploy-steward

Mainline deploy steward. Consumes ready PRs, owns a lease on mainline landing, refreshes PR state, updates stale branches, waits for CI and deploy gates, merges or queues one candidate at a time, and opens repair tasks for failures.

SethGammon/Citadel · 56 tokens

release

CONTRIBUTOR TOOL - Cut a plugin release: bump plugin.json version, finalize CHANGELOG, update README if needed, gate on make ci, commit, tag vX.Y.Z, and create the GitHub release. Use when shipping a new plugin version. NOT distributed.

oliver-kriska/claude-elixir-phoenix · 60 tokens

create-release-checklist

Create a release checklist and GitHub issue for an R package. Use when the user asks to "create a release checklist" or "start a release" for an R package.

posit-dev/skills · 41 tokens

han-release

Cut a Han release: update CHANGELOG.md with the changes since the last release, bump and tag every plugin that changed as {plugin-name}--v{version} so a version-constrained dependency can resolve, and publish a GitHub release crediting every merged pull request and closed issue to the people behind it. Use when…

testdouble/han · 172 tokens

craft-plugin-release

Releasing Craft CMS plugins — tagging, Packagist propagation, GitHub releases, branch promotion, shared-library ordering, history rewrites. ALWAYS load when cutting, preparing, verifying, or debugging a plugin release: bumping a version, dating a changelog, creating or moving a git tag, or checking what Packagist…

michtio/craftcms-claude-skills · 72 tokens

release

Cut a new release: group Conventional Commits since the last tag, append a CHANGELOG section, create a release commit, and add an annotated git tag. TRIGGER when the user says "cut a release", "tag a release", "release v1.2.0", "ship version 1.2.0", "create a release for 1.2.0", "bump the version to 1.2.0", "make a…

thettwe/nyann · 207 tokens