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 davistroy/claude-marketplace --skill shipgit clone --depth 1 https://github.com/davistroy/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/davistroy/claude-marketplace/ship)<a href="https://agentmods.dev/skills/davistroy/claude-marketplace/ship"><img src="https://agentmods.dev/badge/skills/davistroy/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/davistroy/claude-marketplace/ship"><img src="https://agentmods.dev/badge/skills/davistroy/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.00040 | $0.04606 |
| Opus 5 | $0.00020 | $0.02303 |
| Sonnet 5 | $0.00008 | $0.00921 |
| Haiku 4.5 | $0.00004 | $0.00461 |
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 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.
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 — 446 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are automating the complete git workflow to ship code changes. After creating the PR, you will automatically review it, fix any issues, and merge it. The user may provide a branch name and description as arguments: $ARGUMENTS
Pre-loaded Context
The following git state is injected before Claude processes this prompt. Injection is a
load-time precondition — a non-zero exit aborts prompt expansion and the skill never
reaches Claude (ADR-0011 F3), so every command below is guarded to exit 0 everywhere and
reports the sentinel (not a git repository) instead of failing.
Working tree status:
!git status -s 2>/dev/null || echo "(not a git repository)"
Diff summary (unstaged):
!git diff --stat 2>/dev/null || echo "(not a git repository)"
Staged diff summary:
!git diff --cached --stat 2>/dev/null || echo "(not a git repository)"
Current branch:
!git branch --show-current 2>/dev/null || echo "(not a git repository)"
Remote:
!git remote -v 2>/dev/null || echo "(not a git repository)"
Diff size (lines changed):
!git diff HEAD --shortstat 2>/dev/null | grep -oE '[0-9]+ (insertions?|deletions?)' | awk '{s+=$1} END {print s+0}'
The diff-size value is always a bare integer. It counts insertions plus deletions, and
git diff HEAD covers staged and unstaged changes, so the number is correct in the normal
pre-ship state where everything is already git add-ed. Outside a repository it is 0.
Destructive Action Warning
This skill modifies git state (creates branches, commits, pushes, and merges). Before proceeding:
- Confirm the user intends to ship the current changes
- Never force-push or push to main/master directly
- Always create a feature branch for changes
- If the working directory has uncommitted changes that look unrelated, ask before staging everything
Input Validation
Optional Arguments:
<branch-name>- Custom branch name (default: auto-generated from changes)draft- Create PR as draft--dry-run- Preview all operations without making any changes--audit- Log all git and PR operations to.claude-plugin/audit.log(see common-patterns.md)
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 · 446 lines · 40 tokens per session scan A d99e141577f5
ship is a skill published in the GitHub repository davistroy/claude-marketplace (5 stars, last pushed 5d ago), licensed MIT. It adds 40 tokens to every session and 4,606 once invoked, about $0.0002 per session on Opus 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-09-04.
Other skills, from other repositories
review-implement-phase
Implements triaged review actions, commits focused fixes, and posts Done plus resolves threads. Use when the user wants only the implementation phase of the review-framework workflow.
github-pr-workflow
Prepare a GitHub pull request from a feature branch — branch hygiene, commit shape, title/body, verification notes, screenshots for UI work, and replies to review comments.
github-automation
GitHub workflow automation, PR management, issue tracking, and code review coordination. Integrates with GitHub Actions and repository management. Use when: PR creation, code review, issue management, release automation, workflow setup. Skip when: local-only changes, non-GitHub repositories.
review-delta
Review only changes since last commit using impact analysis. Token-efficient delta review with automatic blast-radius detection.
work-unit-commits
Plan commits as reviewable work units. Trigger: implementation, commit splitting, chained PRs, or keeping tests and docs with code.
github-contributor
End-to-end playbook for shipping high-quality pull requests to open-source projects you don't maintain — discovery, CONTRIBUTING compliance, PR-size check, minimal-diff implementation, PR description with AI-assisted disclosure, conflict resolution, and post-submission maintainer interaction. Use whenever creating…