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/hecer/yoke/shipnpx skills add HECer/yoke --skill shipgit clone --depth 1 https://github.com/HECer/yokeWrote 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/hecer/yoke/ship)<a href="https://agentmods.dev/skills/hecer/yoke/ship"><img src="https://agentmods.dev/badge/skills/hecer/yoke/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.00061 | $0.07749 |
| Opus 5 | $0.00030 | $0.03875 |
| Sonnet 5 | $0.00012 | $0.01550 |
| Haiku 4.5 | $0.00006 | $0.00775 |
Grade A, and why
ship scanned grade A with 1 finding 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 3d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -s -o /dev/null -w '%{http_code}' http://localhost:3000 2>/dev/null || \ How it starts
The opening of the file, as written. The whole thing — 692 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ship: Fully Automated Ship Workflow
You are running the ship workflow. This is a non-interactive, fully automated workflow. Do NOT ask for confirmation at any step. The user said /ship which means DO IT. Run straight through and output the PR URL at the end.
Only stop for:
- On the base branch (abort)
- Merge conflicts that can't be auto-resolved (stop, show conflicts)
- In-branch test failures (pre-existing failures are triaged, not auto-blocking)
- Pre-landing review finds ASK items that need user judgment
- MINOR or MAJOR version bump needed (ask — see Step 12)
- AI-assessed coverage below minimum threshold (hard gate with user override — see Step 7)
- Plan items NOT DONE with no user override (see Step 8)
Never stop for:
- Uncommitted changes (always include them)
- Version bump choice (auto-pick MICRO or PATCH — see Step 12)
- CHANGELOG content (auto-generate from diff)
- Commit message approval (auto-commit)
- Multi-file changesets (auto-split into bisectable commits)
- TODOS.md completed-item detection (auto-mark)
- Auto-fixable review findings (dead code, N+1, stale comments — fixed automatically)
Re-run behavior (idempotency):
Re-running ship means "run the whole checklist again." Every verification step runs on every invocation. Only actions are idempotent:
- Step 12: If VERSION already bumped, skip the bump but still read the version
- Step 17: If already pushed, skip the push command
- Step 19: If PR exists, update the body instead of creating a new PR
Step 0: Detect platform and base branch
Detect the git hosting platform from the remote URL:
git remote get-url origin 2>/dev/null
- URL contains "github.com" → platform is GitHub
- URL contains "gitlab" → platform is GitLab
- Otherwise check:
gh auth status 2>/dev/null→ GitHub;glab auth status 2>/dev/null→ GitLab
Determine the base branch (target of the PR, or the repo's default):
- GitHub:
gh pr view --json baseRefName -q .baseRefNameorgh repo view --json defaultBranchRef -q .defaultBranchRef.name - GitLab:
glab mr view -F json 2>/dev/null→ extracttarget_branch - Fallback:
git symbolic-ref refs/remotes/origin/HEAD, thenmain, thenmaster
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.
- 3d ago First seen · 692 lines · 61 tokens per session scan A 80aa59592128
ship is a skill published in the GitHub repository HECer/yoke (2 stars, last pushed 12d ago), licensed MIT. It adds 61 tokens to every session and 7,749 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
release
Create a new release with version bump, release notes, commit, and tag.
release
Skill "release" from ishida-supsys/oretachi, covering release skill, 使い方, 手順, 1. 現在バージョンと次バージョンを決定 and 2. git log を取得.
ship-change
Perform authorized CloudX GitHub mutations and exact-head merge handling after every repository gate is proven.
add-new-agent-support
Add a new agent (tool) support to agent-command-sync following the registry pattern.
with-config
A Codex skill with openai.yaml configuration.
standard-skill
A standard test skill for Gemini.