Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add Zate/cc-plugins/plugin install devloopWrote 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/zate/cc-plugins/ship)<a href="https://agentmods.dev/skills/zate/cc-plugins/ship"><img src="https://agentmods.dev/badge/skills/zate/cc-plugins/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/zate/cc-plugins/ship"><img src="https://agentmods.dev/badge/skills/zate/cc-plugins/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.00014 | $0.01096 |
| Opus 5.5 | $0.00006 | $0.00438 |
| Sonnet 5.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 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.
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.
- 1mo 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 2mo ago), licensed MIT. It adds 14 tokens to every session and 1,096 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
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.
changelog
Auto-generate a changelog from git commits and sprint data. Internal and player-facing versions.
comet-safe-delivery
A Chinese-language procedure for safely delivering specified Comet changes through Git. It covers checking worktrees and unrelated edits, staging exact files, validating hooks, and authorized commits or pushes.
git-workflow
Guided git workflows: prepare PRs, clean up branches, resolve merge conflicts, handle monorepo tags, squash-and-merge patterns. Use when asked to prepare a PR, clean branches, resolve conflicts, or tag a release.
git-push
A GitHub publishing workflow that handles first-time uploads, routine updates, and tagged releases. Git is a system for recording code changes, while GitHub hosts repositories and releases online.
close-task-commit-push-pr
Close the active backlog task (detected from branch name), commit all changes, push to remote, and open a pull request. Use when the user says "close task and ship it", "close task commit push pr", or invokes /close-task-commit-push-pr.