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 commands/ngocsangyem/meowkit/shipgit 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/commands/ngocsangyem/meowkit/ship)<a href="https://agentmods.dev/commands/ngocsangyem/meowkit/ship"><img src="https://agentmods.dev/badge/commands/ngocsangyem/meowkit/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.00000 | $0.00509 |
| Opus 5 | $0.00000 | $0.00254 |
| Sonnet 5 | $0.00000 | $0.00102 |
| Haiku 4.5 | $0.00000 | $0.00051 |
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 today.
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 — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/ship — Phase 5: Ship Pipeline
Usage
/ship
/ship --canary
/ship --dry-run
Behavior
Triggers Phase 5. Runs mk:ship skill. Will NOT execute if Gate 2 (review) has not passed.
Pre-Conditions
Before any shipping action:
- Verify a passing verdict file exists at
tasks/reviews/YYMMDD-name-verdict.md - Verify no FAIL dimensions and no unacknowledged WARNs
- Verify security scan shows no BLOCK items
- If any pre-condition fails: print what's missing and refuse to ship
Execution Steps
-
Pre-ship checks.
- All tests pass (run full test suite).
- No uncommitted changes (working tree clean).
- Branch is up to date with remote.
- Gate 2 verdict file exists and is passing.
-
Create conventional commit.
- Analyze changes to determine commit type:
feat,fix,refactor,docs,test,chore. - Generate commit message following conventional commit format:
type(scope): description Body with details if needed. - Include breaking change footer if applicable.
- Analyze changes to determine commit type:
-
Create Pull Request.
- Push branch to remote.
- Create PR with: title from commit message, body with summary of changes, link to plan file, link to verdict file.
-
Verify CI.
- Wait for CI pipeline to complete.
- If CI fails: parse logs, report the failure, do NOT merge.
- If CI passes: report success.
-
Document rollback plan.
- Print rollback instructions specific to the change:
🐱 Rollback: git revert <commit-sha> && git push - For database migrations: include down-migration command.
- For infrastructure changes: include revert steps.
- Print rollback instructions specific to the change:
Flags
| Flag | Behavior |
|---|---|
--canary |
Staged rollout. Routes to /canary for deployment with monitoring checklist and promotion/rollback decision. |
--dry-run |
Preview everything that would happen (commit message, PR body, files included) without actually pushing or creating the PR. |
Output
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.
- today First seen · 71 lines · 0 tokens per session scan A 45a635ee959d
ship is a command published in the GitHub repository ngocsangyem/MeowKit (14 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 509 tokens. 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 commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.