agentmods.dev

ship-it

ship-it is a skill for Claude Code from nortonx/ai-tooling-free. It costs 61 tokens per session (736 once invoked), scanned A, original, MIT.

A command that prepares current code changes for delivery by creating or selecting a branch, making a commit, and pushing it to the shared remote repository.

In plain words
What is it for?
Use it when you want to branch, commit, and push the current changes, optionally supplying a branch name or issue number.
Why use it?
It combines the routine steps of sending reviewed work to the team while requiring an explicit request and a review of what will be committed.

Skill for Claude Code

Written for Claude Code: argument-hint in frontmatter.

not rated 1repo changed 1mo ago A scan 61 tokens original MIT

Good fit Use it when you want to branch, commit, and push the current changes, optionally supplying a branch name or issue number.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/nortonx/ai-tooling-free/ship-it
View source ↗ nortonx/ai-tooling-free
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 nortonx/ai-tooling-free --skill ship-it
Clone the repo
git clone --depth 1 https://github.com/nortonx/ai-tooling-free

Made for: Claude Code.

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-it

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/nortonx/ai-tooling-free/ship-it"><img src="https://agentmods.dev/badge/skills/nortonx/ai-tooling-free/ship-it.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 61 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 736 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.00061 $0.00736
Opus 5.5 $0.00024 $0.00294
Sonnet 5.5 $0.00012 $0.00147
Haiku 4.5 $0.00006 $0.00074

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

Security

Grade A, and why

ship-it 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.

skills/ship-it/SKILL.md · 45 lines

How it starts

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

Ship it

⚠️ Review the changes first. Show the working-tree status and the commit message you are about to use, and confirm the changes are what is intended: this stages everything, commits, and pushes to remote. Running /ship-it is the user explicit authorization to commit and push for this run (it waives the usual "ask before committing/pushing" rule for this invocation only).

Arguments

[branch-name-or-issue-id]: optional. Overrides the branch name only; the commit message is always auto-derived from the diff.

  • A full branch name (feat/checkout-retry) is used verbatim.
  • A bare issue/ticket id (123) becomes <type>/<issue-id>-<slug>.
  • Omitted -> <type>/<slug> derived from the diff.

(Copilot CLI and skills do not substitute $ARGUMENTS; include the branch name or issue id inline in your prompt when you want to override.)

Steps

  1. Gather context: run: 
    git branch --show-current
git status --short
git diff --stat HEAD
git log --oneline -10
    Resolve the default branch: git symbolic-ref --quiet --short refs/remotes/origin/HEAD (strip the origin/ prefix); fall back to main, else master.
  2. If the working tree is clean, stop and say "nothing to ship". Do nothing else.
  3. Branch:
    • On the default branch (main/master) -> create and switch to a new branch (git switch -c <name>). Name it from the argument if given, else derive <type>/<slug>, where <type> in feat|fix|refactor|docs|test|chore|perf|ci, <slug> = short kebab summary of the change. An issue-id argument like 123 -> <type>/<issue-id>-<slug>.
    • On a feature branch already -> reuse it; do not create another.
  4. Stage everything: git add -A.
  5. Commit following the create-commit-message convention: <type>: <imperative summary, <=72 chars>; reference the issue id from the branch name when present (e.g. (#123) suffix). Focus the summary on the why. One commit only; do not split. Single quotes only if quoting.
  6. Push with upstream tracking: git push -u origin HEAD.
  7. Report in 2 to 3 lines: branch name, commit subject, and push result (include any PR-create hint git prints).

Read the full file on GitHub · 45 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 Changed · -1 tokens per session b5aba5d822b5
  2. 1mo ago First seen · 45 lines · 62 tokens per session scan A 87f55596540f

Subscribe to this mod's changes

ship-it is a skill published in the GitHub repository nortonx/ai-tooling-free (1 stars, last pushed 18d ago), licensed MIT. It adds 61 tokens to every session and 736 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-08-31.

Claude CodeCommitsGit and workflowReleasesai-agentsai-skillscopilot-clideveloper-toolsgemini-cli
Related

Other skills, from other repositories

utility-pm-changelog-curator

Draft CHANGELOG entries from git log via the pm-changelog-curator sub-agent, applying the repo hygiene rules (describe what changed, public paths only, no attribution trailers). Returns a layered draft with a status summary for maintainer review; refuses a dirty working tree unless --committed-only is passed. Use when…

product-on-purpose/pm-skills · 80 tokens

changelog-generator

Generate changelogs and release notes from Conventional Commits with semver bump detection, Keep a Changelog formatting, and monorepo scopes. Use when preparing releases, enforcing commit standards, or automating release notes.

borghei/Claude-Skills · 48 tokens

git-workflow-and-versioning

Use when managing branches, commits, versioning, and release workflows for Android projects, or when cutting a release, choosing a version bump, tagging, or writing a changelog. Covers trunk-based development, atomic commits, versionCode/versionName derived from tags, semver for library modules, changelogs and Play…

GuillemRoca/agent-skills-android · 77 tokens

git

Git init, commit, diff, log, revert, branch, stash, remote.

jxoesneon/Ciel · 19 tokens

git-workflow-and-versioning

Use when committing, choosing a branch or base, resolving conflicts, organizing parallel work streams, integrating a finished branch (local merge, PR, keep-as-is), cutting a release, picking a semantic version bump, tagging, or writing a changelog. Not for creating or cleaning up an isolated workspace (use…

oleg494/coding-kit · 95 tokens

git-conventions

Apply when committing, branching, or opening a pull request. Conventional commit format, branch naming, PR scope.

sordi-ai/skill-everything · 26 tokens