Borrowing it
Nothing to install: this file belongs to EricAndrechek/Pacer. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/EricAndrechek/Pacer/main/.claude/skills/ship/SKILL.mdgit clone --depth 1 https://github.com/EricAndrechek/PacerWrote 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/ericandrechek/pacer/ship)<a href="https://agentmods.dev/skills/ericandrechek/pacer/ship"><img src="https://agentmods.dev/badge/skills/ericandrechek/pacer/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/ericandrechek/pacer/ship"><img src="https://agentmods.dev/badge/skills/ericandrechek/pacer/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.00138 | $0.01480 |
| Opus 5.5 | $0.00055 | $0.00592 |
| Sonnet 5.5 | $0.00028 | $0.00296 |
| Haiku 4.5 | $0.00014 | $0.00148 |
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 21d 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 — 117 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ship a Pacer release
This skill is the orchestration and the gate. The deterministic plumbing —
computing the next version, tagging, watching the Release workflow, verifying
the published artifact — is in bin/ship.sh. Read docs/releasing.md for the
pipeline and one-time setup.
There is exactly ONE human gate: a single approval right after a local install. Everything after it is autonomous and backgrounded. The whole point is that a release costs almost no attention (and almost no expensive model tokens): the waiting and verifying happen in a backgrounded script, and the draft/review chores go to a cheap model.
0 · Before a release (during the work)
- Branches and PRs are your judgement — stack/rename branches freely as scope grows, push for backup whenever. Do not open the PR yet, and never tag/merge here.
- When the work is done,
make installso the maintainer can see it live. Stop there.
1 · The gate — right after make install is live
bin/ship.sh preflight→ prints the suggested bump (patch, or minor if a@Model/schema change is detected — you confirm; minor = a SwiftData reset) and the next version.bin/ship.sh notes <version>→ previews the exact notes CI will publish (--generate-notes), so what you show matches what ships.- Surface bump + notes:
- Not pre-authorized → ask once with
AskUserQuestion(it push- notifies the maintainer and blocks). Offer: ship it · hold · change the bump. This is the only AskUserQuestion in the flow. - Pre-authorized — the kickoff request already said to ship ("…and
release it", "ship it autonomously", "merge and release") → send a
PushNotificationFYI with the bump + notes, then proceed.
- Not pre-authorized → ask once with
The only other permitted interruption anywhere is a genuine implementation/ direction fork you shouldn't guess on.
2 · Prep — into the PR, before merge
Do the release housekeeping and commit it to the branch before merging (so the shipped PR is self-contained):
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.
- 21d ago Changed · +8 lines d6b96ca94dfa
- 1mo ago Changed · +2 lines fc96fd626e38
- 1mo ago First seen · 107 lines · 138 tokens per session scan A 6895b0c10d93
ship is a skill published in the GitHub repository EricAndrechek/Pacer (11 stars, last pushed today), licensed MIT. It adds 138 tokens to every session and 1,480 once invoked, about $0.0006 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
release
Build, sign, notarize, and publish a new DroidProxy release. Use when the user wants to cut a release, merge a PR and ship it, or asks to build/notarize/publish. Covers the full pipeline: PR merge, version bump, swift build, code signing, Apple notarization, Sparkle appcast update, and GitHub release creation.
version-bump
Automated semantic versioning and release workflow for Claude Code plugins. Handles version increments across package.json, marketplace.json, plugin.json manifests, build verification, git tagging, GitHub releases, and changelog generation. npm publishing is done by the tag-triggered GitHub Actions workflow through…
batch
Research and plan a large-scale change, then execute it in parallel across 5–30 isolated worktree agents that each open a PR.
github
GitHub via gh CLI: PRs, issues, reviews, repos, auth.
changelog
Auto-generate a changelog from git commits and sprint data. Internal and player-facing versions.
release
Fully automate a release with version-bump and childhood.