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 imisic/claude-marketplace --skill shipgit clone --depth 1 https://github.com/imisic/claude-marketplaceWrote 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/imisic/claude-marketplace/ship)<a href="https://agentmods.dev/skills/imisic/claude-marketplace/ship"><img src="https://agentmods.dev/badge/skills/imisic/claude-marketplace/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/imisic/claude-marketplace/ship"><img src="https://agentmods.dev/badge/skills/imisic/claude-marketplace/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.00022 | $0.00692 |
| Opus 5.5 | $0.00009 | $0.00277 |
| Sonnet 5.5 | $0.00004 | $0.00138 |
| Haiku 4.5 | $0.00002 | $0.00069 |
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 23d 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.
How it starts
The opening of the file, as written. The whole thing — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ship Pipeline
Review, fix, and commit in one flow, pausing after the review so nothing gets fixed or committed until you have seen what was found.
This skill assumes the project already has a review skill (the kind a-review-optimizer, in the dev-workflow-forge plugin, generates: a project-tuned *-review skill in .claude/skills/). If none exists, say so and suggest running a-review-optimizer first.
Flags
| Flag | Effect |
|---|---|
--no-fix |
Skip the fix phase, go review -> commit |
--no-commit |
Stop after the fix phase |
--deploy |
Run the project's deploy step after commit, if one exists |
| Other flags | Pass through to the project's review skill (e.g. --full, --debt, --security-only) |
Default review scope is changed files only.
Phase 1: Review
Invoke the project's review skill with all pass-through flags (default: changed files only).
Wait for it to finish. Capture the full report.
Gate 1: Review Results
Show a compact summary of findings by severity (Critical/High/Medium/Low counts).
- Zero findings: print "Clean review. Skipping fix phase." and jump to Phase 3.
- Findings exist: ask the user: "Fix these? (yes / skip to commit / abort)"
- yes -> Phase 2
- skip to commit -> Phase 3
- abort -> stop, print "Aborted."
If --no-fix was passed, skip this gate and go straight to Phase 3.
Phase 2: Fix
Feed the full review report to /fix (batch mode; it parses the severity markers and file:line table on its own).
Wait for fixes to complete before moving on.
Phase 3: Commit
Skip if --no-commit was passed. Print "Stopped after fix phase." and end.
Otherwise invoke /commit.
Phase 4: Suggest Deploy
After a successful commit:
- If
--deploywas passed and the project has a deploy step (a build script, a deploy command, a CI trigger): run it. - If
--deploywas passed and no deploy step exists: say so plainly; don't invent one. - Otherwise: print a reminder that the project's own deploy step (if any) is the next manual action.
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.
- 23d ago Changed · +4 lines · +3 tokens per session 111f3125b473
- 1mo ago First seen · 63 lines · 19 tokens per session scan A 6433273b0c96
ship is a skill published in the GitHub repository imisic/claude-marketplace (1 stars, last pushed 11d ago), licensed MIT. It adds 22 tokens to every session and 692 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.
Other skills, from other repositories
git-workflow
Git workflow and conventional commits. Use when working with git, branches, commits, pull requests, code review, or version control strategy.
shipit
Turn finished work into a clean commit and pull request. Always asks first whether the commit and PR should carry AI/bot authorship attribution or stay fully human-authored, then matches the repository's existing commit conventions, splits work into logical commits, and writes a PR body with context, risk, and…
pr-review-fix-pipeline
Reviews a PR and applies fixes for the non-controversial findings: review, fix, test, and commit in one pass. Writes code, so use it only on feature branches where automatic edits are fine. Trigger on: "review and fix PR", "auto-fix the PR", "review PR #X and fix issues", "run the review pipeline".
pr-generator
Use this skill when creating a pull request — generate the title, structured description, and review checklist from the branch's actual commits and diff. Don't use it for commit messages (git-commit skill) or changelogs.
contribute
Complete contribution workflow using git-town. Create branch → commit → PR → ship. Preflight at every step.
eg-precommit-review
Run a Codex-native pre-commit independent-review loop on pending changes.