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/joncik91/ucai/cancel-shipgit clone --depth 1 https://github.com/Joncik91/ucaiWrote 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/joncik91/ucai/cancel-ship)<a href="https://agentmods.dev/commands/joncik91/ucai/cancel-ship"><img src="https://agentmods.dev/badge/commands/joncik91/ucai/cancel-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.00004 | $0.00378 |
| Opus 5 | $0.00002 | $0.00189 |
| Sonnet 5 | $0.00001 | $0.00076 |
| Haiku 4.5 | $0.00000 | $0.00038 |
Grade A, and why
cancel-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
Cancel Ship
To cancel the ship pipeline:
-
Check if
.claude/ucai-ship.local.mdexists using Bash:test -f .claude/ucai-ship.local.md && echo "EXISTS" || echo "NOT_FOUND" -
If NOT_FOUND: Say "No active ship pipeline found."
-
If EXISTS:
- Read
.claude/ucai-ship.local.mdto get the current phase, milestone, and any worktree/branch info - Remove the file using Bash:
rm .claude/ucai-ship.local.md - Report: "Cancelled ship pipeline (was at Phase N: PhaseName, milestone: M)"
- Read
-
Cleanup warnings (check each, report what applies):
- Run
git worktree list— if a ship worktree exists, warn: "Ship worktree still exists at [path]. Rungit worktree remove [path]to clean up, or inspect it first." - If the state file mentioned a branch that was pushed, warn: "Remote branch [name] may still exist. Run
git push origin --delete [name]if you want to remove it." - If a PR was created, warn: "A PR may have been created. Check your GitHub repo and close it if no longer needed."
- Run
-
Do NOT auto-delete worktrees, branches, or PRs — the user decides what to keep.
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 · 26 lines · 4 tokens per session scan A 0cb2e9a10147
cancel-ship is a command published in the GitHub repository Joncik91/ucai (29 stars, last pushed 10d ago), licensed MIT. It adds 4 tokens to every session and 378 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-08-30.
Other commands, from other repositories
version-bump
Bump versions across the monorepo during release process.
release
Bump version, commit, push, mirror to ai-skills, and update local plugin.
ship
Branch, commit, open PR, gather Claude + every enabled AI reviewer (Copilot, CodeRabbit, etc.), fix/justify/resolve every finding, loop until clean, then merge. Run only when implementation is finished AND the owner has said to ship (e.g. "ship it") — never self-invoke just because the work looks done. To design and…
release
Prepare a release of the sonu plugin — decide the semver bump, sync the version and plugin description across all five homes, run /validate, then hand to /sonu:ship. Only meaningful inside the claude-plugins repo; in any other repo, say so and stop.
release-notes
Assemble release notes / a changelog entry for a commit range, even from non-conventional history.
version-guard
Classify API-surface changes as breaking or non-breaking and recommend a semver bump.