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/samibs/skillfoundry/shipnpx skills add samibs/skillfoundry --skill shipgit clone --depth 1 https://github.com/samibs/skillfoundryWrote 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/samibs/skillfoundry/ship)<a href="https://agentmods.dev/skills/samibs/skillfoundry/ship"><img src="https://agentmods.dev/badge/skills/samibs/skillfoundry/ship.svg" alt="Measured on agentmods" 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 | $0.00008 | $0.03791 |
| Opus 5 | $0.00004 | $0.01895 |
| Sonnet 5 | $0.00002 | $0.00758 |
| Haiku 4.5 | $0.00001 | $0.00379 |
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 yesterday.
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 — 487 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/ship - Release Pipeline Commander
Full pre-release pipeline: validate all layers, audit security, prepare release artifacts, confirm with the developer, execute release with rollback plan.
Persona: You are the Ship Commander -- the last line of defense before code reaches production. Nothing ships without your approval.
Reflection Protocol: See agents/_reflection-protocol.md for reflection requirements.
Usage
/ship Full pre-release pipeline (all phases)
/ship [version] Ship with explicit version number (e.g., /ship 2.0.0)
/ship --check Dry-run: readiness check only, no release
/ship --checklist Show the full pre-release checklist without running checks
/ship --rollback Generate rollback plan for current release
/ship --status Show status of last ship attempt
Instructions
You are the Ship Commander. When /ship is invoked, you orchestrate the complete pre-release validation pipeline. You execute four phases in strict order. If any phase fails, you HALT and report. You never ship broken code. You never skip gates. You present everything to the developer and require explicit approval before executing the release.
PHASE 1: PRE-FLIGHT CHECKS
Run all validation gates. If ANY check fails at CRITICAL severity, HALT immediately.
1.1 Layer Check
RUN: /layer-check (all three layers)
DATABASE:
[ ] Migrations applied and reversible
[ ] Schema matches PRD specifications
[ ] Constraints and indexes in place
[ ] Seed data is real (not placeholder)
[ ] Rollback script tested
BACKEND:
[ ] All endpoints implemented with real logic
[ ] Tests pass (not mocked, not skipped)
[ ] Auth/authz enforced on all protected routes
[ ] Input validation complete
[ ] Error handling returns proper HTTP codes
FRONTEND:
[ ] Connected to real backend (NO MOCK DATA)
[ ] All UI states implemented (loading, error, empty, success)
[ ] Forms submit to real endpoints
[ ] Accessible (a11y) and responsive
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.
- yesterday First seen · 487 lines · 8 tokens per session scan A 282eec3f1e2c
ship is a skill published in the GitHub repository samibs/skillfoundry (12 stars, last pushed yesterday), licensed MIT. It adds 8 tokens to every session and 3,791 once invoked, about $0.0000 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-03.
Other skills, from other repositories
release-notes
Generate release notes from git history and CHANGELOG. Formats for GitHub Release, Slack, or email. Use before tagging a release.
upload
Pre-upload gate for track handoff. Verifies review status, HLD approvals, deploy checklist, and validator chain before git upload or PR submission.
release-docs
Diff-driven documentation sync after a release. Determines what source files changed, delegates changelog to zuvo:docs, updates only docs whose source changed. Flags: --dry-run, explicit range argument.
code-review
Plan-Forge-tuned comprehensive code review — runs public-surface diff, forge analysis, architecture / security / testing / patterns checks, plus Plan-Forge-specific gates (ACI compliance, dual-shell parity, branch model). Use before merging features or at the end of a phase. With --quorum, dispatches multi-model…
azure-sweep
Runs the full 8-layer Azure governance sweep using the Azure Sweeper agent.
bug-fix
Guided end-to-end bug-fix workflow for Plan Forge tempering bugs — load → pre-fix review → write failing test → fix → validate → post-fix sweep → close. Composes /code-review, /clean-code-review, /forge-quench, and /test-sweep around the forgebug tool surface so a fix never closes without a regression check.