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/eigent-ai/agent-skills/shipnpx skills add eigent-ai/agent-skills --skill shipgit clone --depth 1 https://github.com/eigent-ai/agent-skillsWrote 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/eigent-ai/agent-skills/ship)<a href="https://agentmods.dev/skills/eigent-ai/agent-skills/ship"><img src="https://agentmods.dev/badge/skills/eigent-ai/agent-skills/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.1 | $0.00053 | $0.00439 |
| Opus 5 | $0.00026 | $0.00219 |
| Sonnet 5 | $0.00011 | $0.00088 |
| Haiku 4.5 | $0.00005 | $0.00044 |
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 6d 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.
What it actually says
Ship
Overview
Use this skill to prepare a feature or change for production. The goal is to make launch decisions explicit: what ships, how it rolls out, what is monitored, when to stop, and how to recover.
Workflow
- Identify the release scope, owner, timeline, users affected, dependencies, and risk level.
- Build a pre-launch checklist:
- Tests, migrations, feature flags, documentation, support readiness, analytics, alerts, and runbooks.
- Define rollout strategy:
- Internal, beta, percentage rollout, region/account cohorts, or all-at-once when low risk.
- Specify success metrics and guardrails:
- Product metrics, reliability metrics, error rates, latency, revenue, support volume, and user feedback.
- Create rollback and mitigation steps:
- Flag disablement, revert path, data repair, comms, and owner escalation.
- Plan launch communications for affected teams and users.
- After launch, compare live metrics against expected ranges and decide whether to continue, pause, expand, or roll back.
Output Pattern
- Release summary.
- Pre-launch checklist.
- Rollout stages and entry/exit criteria.
- Monitoring plan.
- Rollback plan.
- Communications plan.
- Post-launch validation steps.
Example Prompts
/ship - We're deploying the new payments flow tomorrow. Walk me through the pre-launch checklist, what to monitor in the first hour, and our rollback plan if error rates spike./ship - Plan a staged rollout for our new recommendation engine. Start at 5% traffic, define success metrics, and set the criteria for each expansion step to 100%./ship - We shipped 3 hours ago. Here are the current metrics [paste]. Is anything outside normal range? Should we roll back or keep going?
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.
- 6d ago First seen · 41 lines · 53 tokens per session scan A 824133da600b
ship is a skill published in the GitHub repository eigent-ai/agent-skills (17 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 53 tokens to every session and 439 once invoked, about $0.0003 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-08-30.
Other skills, from other repositories
release-announcement
Write a release announcement — changelog, blog post, in-app note, or social post — that leads with user impact, names the audience, and includes upgrade/migration steps without filler.
agent-release-swarm
Agent skill for release-swarm - invoke with $agent-release-swarm.
release
Cut a Symphony release by bumping the committed version, landing it, tagging the merged commit, and verifying the Burrito release workflow. Use when asked to release, tag, or retag Symphony.
changelog
Create changelog files for important commits in a PR.
multi-agent-release-manager
Cleans up the workspace, formats code, runs presubmit checks, and uploads CLs to Gerrit.
refresh-arm-sdk-release
WORKFLOW SKILL — Prepares Azure.ResourceManager SDK refresh pull requests in azure-sdk-for-net. WHEN: "prepare sdk refresh", "refresh Azure.ResourceManager package", "update ARM SDK from autorest tag", "refresh changelog dependencies". INVOKES: git and GitHub pull request tools for branch, commit, push, and PR…