agentmods.dev

ship

ship is a skill for Claude Code from urmzd/dotfiles. It costs 119 tokens per session (629 once invoked), scanned A, original, Apache-2.0.

A Git workflow helper that creates a standard commit message from your changes, makes a commit, and can optionally push it and monitor the automated checks. Git is a tool for tracking code changes; CI checks those changes automatically.

In plain words
What is it for?
Use it to commit current work, optionally push the branch, watch CI, and show useful error logs when checks fail.
Why use it?
It removes the repetitive work of reviewing changes, choosing a commit format, and checking whether pushed code passes automated checks. It also avoids accidentally committing common secret files such as .env files and private keys.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

not rated 5repo +1 6d ago A scan 119 tokens original Apache-2.0

Good fit Use it to commit current work, optionally push the branch, watch CI, and show useful error logs when checks fail.

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

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

README.md
[![agentmods](https://agentmods.dev/badge/skills/urmzd/dotfiles/ship/github.svg)](https://agentmods.dev/skills/urmzd/dotfiles/ship)
Your own site
<a href="https://agentmods.dev/skills/urmzd/dotfiles/ship"><img src="https://agentmods.dev/badge/skills/urmzd/dotfiles/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/urmzd/dotfiles/ship"><img src="https://agentmods.dev/badge/skills/urmzd/dotfiles/ship.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 119 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 629 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.00119 $0.00629
Opus 5.5 $0.00048 $0.00252
Sonnet 5.5 $0.00024 $0.00126
Haiku 4.5 $0.00012 $0.00063

Measured 1mo ago against content hash 79d20fa4a310, 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.

dot_agents/skills/ship/SKILL.md · 46 lines

What it actually says

Ship

Commit, push, and watch the CI pipeline.

Steps

  1. Stage changes: Run git status --porcelain. If there are unstaged/untracked changes, stage them (prefer specific files over git add -A; never stage .env or credential files).

  2. Commit: If a message argument is provided, use it. Otherwise, generate a conventional commit message from the diff (feat:, fix:, chore:, docs:, refactor:, test:). Use the repo's recent git log --oneline -10 to match style.

  3. Push (optional): Only if the user wants to push. Run git push. If no upstream is set, use git push -u origin HEAD. If the user only asked for a commit, stop here and report the commit.

  4. Watch CI (optional): After push, run gh run list --branch $(git branch --show-current) --limit 1 --json databaseId,status,conclusion in a loop (max 5 minutes, poll every 15s). Report the final status.

  5. On failure: If CI fails, run gh run view <id> --log-failed and show the relevant error output so the user can decide next steps.

Rules

  • Never commit files that look like secrets (.env, credentials.json, *.pem, *.key).
  • Never force push.
  • If there are no changes to commit, say so and stop.
  • If CI isn't set up (no workflows found), just push and report that there's no CI to watch.

Gotchas

  • The gh run is not registered immediately after git push. Poll with retry (a few attempts, a couple seconds apart) before concluding "no run found" -- the run may take several seconds to appear.
  • If git push is rejected by branch protection (protected branch, required reviews, required status checks), stop and report the rejection. Do not retry, force push, or attempt to bypass protection.
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 · 46 lines · 119 tokens per session scan A 79d20fa4a310

Subscribe to this mod's changes

ship is a skill published in the GitHub repository urmzd/dotfiles (5 stars, last pushed 6d ago), licensed Apache-2.0. It adds 119 tokens to every session and 629 once invoked, about $0.0005 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.

CommitsGit and workflowchezmoidotfilesneovimnvimtmuxzsh
Related

Other skills, from other repositories

scan-commit

Automatically scan the repository for unstaged/untracked changes, group them into logical commits using hunk-level analysis, stage and commit them following Conventional Commits.

magic3007/dotfiles · 35 tokens

smart-commit

Analyze staged changes and split them into multiple logical commits following Conventional Commits.

magic3007/dotfiles · 19 tokens

create-pr

Rebase from the latest origin/main, squash the commits from it, and then create a PR on github with intelligent commit messages based on staged changes.

magic3007/dotfiles · 34 tokens

gen-commit-msg

Generate intelligent commit messages based on staged changes following Conventional Commits format.

magic3007/dotfiles · 19 tokens

commit

Commit the changes in the working tree. Only invoke when the user explicitly signals to commit ("commit", "/commit", etc.). Never invoke this skill on your own initiative — implementation approval is not a commit signal.

ooloth/dotfiles · 44 tokens

smart-commit

Analyzes all uncommitted changes (staged and unstaged), groups them into atomic commits by logical purpose, and generates clear conventional commit messages with practical, context-rich bodies. Use when the user asks to "smart commit", "group my commits", "split into atomic commits", "organize my changes into…

wunki/dotfiles · 134 tokens