Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/static-var/Keystonenpx agentmods add skills/static-var/keystone/shippingWrote 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/static-var/keystone/shipping)<a href="https://agentmods.dev/skills/static-var/keystone/shipping"><img src="https://agentmods.dev/badge/skills/static-var/keystone/shipping/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/static-var/keystone/shipping"><img src="https://agentmods.dev/badge/skills/static-var/keystone/shipping.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.00111 | $0.02732 |
| Opus 5.5 | $0.00044 | $0.01093 |
| Sonnet 5.5 | $0.00022 | $0.00546 |
| Haiku 4.5 | $0.00011 | $0.00273 |
Grade A, and why
shipping 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 — 188 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Shipping
Core principle
Shipping is deterministic finalization for already-completed work. It proves, reviews, packages, and hands off a release or PR; it never sneaks in new implementation or last-mile fixes.
A shipping decision consumes three shared contracts: load ../_shared/gates/proof.md, ../_shared/gates/review.md, and ../_shared/gates/ship.md. Those files own pass/fail; Shipping gathers evidence and performs explicitly authorized delivery mechanics.
If a final check fails, follow its owning gate's fail action. Final delivery remains blocked until the required gates pass.
Load when
Load only when the user explicitly asks to deliver completed software project work: commit it, push it, prepare or create a PR, merge, tag, package, publish, release, deploy, or perform an exact repository handoff or destructive cleanup of a named completed-delivery target.
For a Keystone handoff, load ../_shared/handoff-packet.md. The canonical packet's
evidence field must carry the verbatim user delivery request and exact authorized
action set. Before acting, derive the effective action set using the packet's
current-intent reconciliation rule. A handoff without carried authorization does not
qualify for Shipping.
At entry, use the full Keystone path when an identified repository change, package, release candidate, or deployment is complete enough for gates and the user has explicitly requested a delivery outcome. Handle ordinary summaries, status updates, and non-project handoffs directly. Explicit skill invocation selects the Shipping workflow; commit, push, prepare or create a PR, merge, tag, package, publish, release, deploy, perform an exact repository handoff, or perform destructive cleanup of an exact completed-delivery target only when that action is in the user's authorized action set and the gates authorize it.
Not for
- Starting new implementation or sneaking in last-minute fixes.
- Unfinished code, product, migration, or feature cleanup; route that work to
implementation. Shipping owns destructive cleanup only for an exact completed-delivery target under explicit user authorization. - Root-cause debugging; use
root-cause-analysis. - Fixing test/build/package failures; use
implementationfor contained repairs orroot-cause-analysiswhen the cause is unclear. - General project risk audits; use
project-audit. - Reviewing code quality of a specific change; use
change-review. - Shaping unfinished requirements; use
product-planning. - Bypassing proof, change-review, package, deploy, or human release approvals.
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 · 188 lines · 111 tokens per session scan A 380c75562f74
shipping is a skill published in the GitHub repository static-var/Keystone (6 stars, last pushed 3mo ago), licensed MIT. It adds 111 tokens to every session and 2,732 once invoked, about $0.0004 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
create-release
Use when the user asks to "create a release", "cut a release", "tag a version", "publish release notes", or ship a new versioned GitHub release for the current repo.
sync-docs-release
Use when the user wants to sync docs and then cut a release in one shot. Combines sync-docs (which lands its edits through its own docs PR) → optional merge of that PR → create-release in sequence. Triggers on phrases like "sync docs and release", "sync and cut a release", "update docs and publish a release".
branch-finish
You MUST use this when verified development work is ready for an integration or handoff decision - merging, pushing, opening a pull request, preserving or discarding a branch, or cleaning up its workspace. Covers safe completion choices based on the actual Git state and verification evidence.
github-release
Guides IA through releasing a new version of a GitHub library end-to-end. Handles SemVer versioning and Keep a Changelog formatting automatically.
create-github-pull-request-from-specification
Create GitHub Pull Request for feature request from specification file using pullrequesttemplate.md template.
antigravity-maintainer-batch-release
Run protected AAS maintainer sweeps, PR merge batches, resumable review, immutable distribution, Core checks, and scripted releases. Use for repository maintenance, main alignment, CLI/MCP/Workbench c.