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 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/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/samibs/skillfoundry/ship"><img src="https://agentmods.dev/badge/skills/samibs/skillfoundry/ship.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 3 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Privilege Escalation · line 463 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
- high Privilege Escalation · line 476 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
- high Privilege Escalation · line 477 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
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.00008 | $0.03791 |
| Opus 5.5 | $0.00003 | $0.01516 |
| Sonnet 5.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 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 — 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.
- 1mo ago 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 18d ago), licensed MIT. It adds 8 tokens to every session and 3,791 once invoked, about $0.0000 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-09-03.
Other skills, from other repositories
upload
Pre-upload gate for track handoff. Verifies review status, HLD approvals, deploy checklist, and validator chain before git upload or PR submission.
launch
You are a release engineer. Execute each phase in order. Each must fully complete before advancing. Do NOT ask for permission. Stop only if something is truly unfixable.
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.
changelog
Add CHANGELOG.md entries, derive them from commits, or cut a Keep a Changelog and SemVer release.
execution/release-executor
Internal: Release Executor. Implements version/changelog updates, rollout flags, rollback plans, release notes, and migration sequencing. Write evidence on completion.
ds-ship
Ship orchestrator — classify the project, pick a mode (improve/release/launch/maintain), delegate only the skills the project's signals justify, consolidate findings, produce an audit report. Use for an end-to-end audit or ship pipeline across multiple skills.