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 agentmods add skills/zate/cc-plugins/shipnpx skills add Zate/cc-plugins --skill shipgit clone --depth 1 https://github.com/Zate/cc-pluginsWhat 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 | $0.00014 | $0.01096 |
| Opus 5 | $0.00007 | $0.00548 |
| Sonnet 5 | $0.00003 | $0.00219 |
| Haiku 4.5 | $0.00001 | $0.00110 |
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 2d 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 — 173 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ship - Commit and PR
Validate and ship changes with branch-aware workflow. You do the work directly.
Bash hygiene: prefer quiet flags to minimize output (npm install --silent, git status -sb, pipe long output through | tail -n 20).
Phase 1: Pre-flight Check
git status && git diff --stat && git branch --show-current
Read .devloop/local.md for preferences: git.pr-on-complete, commits.style.
| Branch | Flow |
|---|---|
| main/master | Direct commit (caution) |
| feat/, fix/ | Feature branch → PR |
| Other | Ask user |
AskUserQuestion:
questions:
- question: "How would you like to ship?"
header: "Mode"
multiSelect: false
options:
- label: "Full validation"
description: "Run tests, review, then commit/PR"
- label: "Quick commit"
description: "Skip validation, just commit"
- label: "PR only"
description: "Changes already committed, create PR"
- label: "Atomic commits"
description: "One commit per completed plan task"
Phase 2: Validation (if Full mode)
Run tests: Detect from package.json/go.mod/requirements.txt/pom.xml.
Code review: If review.before-commit: always, use devloop:engineer in reviewer mode.
Safety: No secrets, no debug code, correct branch.
Phase 3: Smart Commit
If plan exists:
- Find tasks marked
[x]since last commit - Offer: single commit vs atomic commits
Conventional style:
<type>(<scope>): <description>
- Task 1.1: Description
- Task 1.2: Description
| Task Contains | Type |
|---|---|
| Create, Add, Implement | feat |
| Fix, Resolve | fix |
| Refactor, Clean | refactor |
| Test, Spec | test |
| Doc, README | docs |
| Other | chore |
Issue closing: If plan has issue: in frontmatter:
github.auto_close: always→ Auto-addCloses #Ngithub.auto_close: ask→ Promptgithub.auto_close: never→ Skip
git add -A && git commit -m "$(cat <<'EOF'
feat(scope): description
- Task 1.1: Description
- Task 1.2: Description
Closes #42
EOF
)"
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.
- 2d ago First seen · 173 lines · 14 tokens per session scan A f890b380d486
ship is a skill published in the GitHub repository Zate/cc-plugins (10 stars, last pushed 1mo ago), licensed MIT. It adds 14 tokens to every session and 1,096 once invoked, about $0.0001 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-08-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…