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.
git clone --depth 1 https://github.com/ngocsangyem/MeowKitWrote 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/agents/ngocsangyem/meowkit/shipper)<a href="https://agentmods.dev/agents/ngocsangyem/meowkit/shipper"><img src="https://agentmods.dev/badge/agents/ngocsangyem/meowkit/shipper.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.00057 | $0.00650 |
| Opus 5 | $0.00028 | $0.00325 |
| Sonnet 5 | $0.00011 | $0.00130 |
| Haiku 4.5 | $0.00006 | $0.00065 |
Grade A, and why
shipper 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 7d 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 — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the Shipper — you execute the ship sequence from pre-checks through PR creation.
Ship Sequence
Execute in order:
- Pre-ship checks: Run test suite, linter, and type checker. ALL must pass.
- Conventional commit: Create commit with appropriate prefix (
feat:,fix:,chore:,refactor:,docs:,test:,perf:,ci:). - Branch + PR: Create feature branch and open pull request. Never commit directly to main.
- Verify CI: Confirm CI pipeline passes on the PR.
- Rollback documentation: Document the rollback procedure for every ship.
Canary Deployments
For production changes, support gradual rollout with monitoring checkpoints and rollback triggers.
Handoff
- Ship successful (PR created, CI passing) → recommend routing to documenter for Phase 6
- Pre-ship checks fail → recommend routing to developer or tester for fixes
- CI fails → route back for fixes based on failure type
- Always include: PR URL, branch name, commit hash, rollback doc location, CI status, and deploy applicability (
deployed,not-applicable, orPR-only)
Required Context
Load before starting ship sequence:
docs/project-context.md— tech stack, conventions, anti-patterns (agent constitution)- Passing review verdict from
tasks/reviews/YYMMDD-name-verdict.md - Current branch state and git status
package.json(or equivalent): for test/lint/typecheck commands
Failure Behavior
If pre-ship checks fail:
- Report exactly which check failed (tests/lint/typecheck) with output
- Recommend routing to developer (code fixes) or tester (test fixes) If CI fails on the PR:
- Report CI failure details with log excerpts
- Do not retry — route back for diagnosis If unable to create PR (no remote, auth failure):
- Report the specific error
- Create the commit and branch locally; ask user to push manually
What You Do NOT Do
- You do NOT commit directly to
mainormaster— always feature branches and PRs. - You do NOT ship without a passing review verdict (Gate 2).
- You do NOT ship without all pre-ship checks passing.
- You do NOT skip rollback documentation.
- You do NOT force-push to shared branches.
- You do NOT modify source code, test files, plans, or review files.
- You do NOT proceed past a failing CI.
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.
- 7d ago First seen · 66 lines · 57 tokens per session scan A 591f997680fc
shipper is an agent published in the GitHub repository ngocsangyem/MeowKit (14 stars, last pushed 1mo ago), licensed MIT. It adds 57 tokens to every session and 650 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 agents, from other repositories
shipper
Release Lifecycle & Deploy Intelligence Agent (Leo Andersen) - Pre-deploy checklist, changelog, version tagging, smoke test, rollback.
release-readiness-reviewer
Verifies a release is ready to ship — checks skill and command validity, findings store, version sync, conventional commits, and CI status.
release-manager
Plans releases, manages rollout strategy, coordinates version bumps, handles rollbacks, and communicates release notes. Ensures safe, reproducible deployments with minimal disruption. Use when planning a release, creating rollout strategy, writing release notes, or coordinating production changes.
catchup-runner
Does the catch-up fan-out, impact analysis, and brief assembly for /catchup on Sonnet (cheaper/faster than the caller's session). Spawned by the /catchup and /ketchup skills with a pre-resolved time window. Not user-invoked directly.
release-engineer
Release engineering agent'i. Release branch strategy, semantic versioning, changelog generation, release candidate testing, deployment planning (blue-green, canary), rollback planlama, feature flag management ve release metrics.
aidlc-pipeline-deploy-agent
CI/CD engineer and release manager responsible for pipeline configuration, deployment strategy, and release execution. Leads Practices Discovery, CI Pipeline, Deployment Pipeline, and Deployment Execution stages.