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 skills add stefan-jansen/coding-agent-toolkit --skill shipgit clone --depth 1 https://github.com/stefan-jansen/coding-agent-toolkitWrote 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/stefan-jansen/coding-agent-toolkit/ship)<a href="https://agentmods.dev/skills/stefan-jansen/coding-agent-toolkit/ship"><img src="https://agentmods.dev/badge/skills/stefan-jansen/coding-agent-toolkit/ship/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/stefan-jansen/coding-agent-toolkit/ship"><img src="https://agentmods.dev/badge/skills/stefan-jansen/coding-agent-toolkit/ship.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00048 | $0.02846 |
| Opus 5.5 | $0.00019 | $0.01138 |
| Sonnet 5.5 | $0.00010 | $0.00569 |
| Haiku 4.5 | $0.00005 | $0.00285 |
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 14d 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 — 264 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ship — close out the active milestone
You are running the SHIP step of the workflow. Your job is to take
the milestone's open PR — built up one commit at a time by /next-issue — and
land it on the default branch, then verify that all milestone issues auto-closed
and close the milestone.
This step is host-neutral: same contract on Claude and Codex. The verbs are
gh and git.
Arguments
Parse these from the user's invocation (any order):
| Arg | Required | Default | Meaning |
|---|---|---|---|
--repo <owner/name> |
no | current repo via gh repo view --json nameWithOwner --jq .nameWithOwner |
Target GitHub repo |
--milestone <title> |
no | the active milestone (resolved as in /next-issue) |
Restrict to this milestone |
--pr <N> |
no | the open PR whose milestone matches | Override PR pick |
--no-delete-branch |
no | false (delete) | Keep the feature branch after merge |
--no-close-milestone |
no | false (close) | Leave the milestone open after merge |
--dry-run |
no | false (act) | Print what would happen, change nothing |
Default behavior is to act, not dry-run — landing the PR is the point of
the verb. --dry-run is for "show me the ship checklist" without merging.
What "active milestone" means
Same resolution as /next-issue:
- List open milestones:
gh api "repos/<owner>/<repo>/milestones?state=open" --jq '.[].title'. - One open → pick it.
- Multiple → ask the user, listing them with open-issue counts.
- Zero → tell the user there's nothing to ship and stop.
What "the milestone's PR" means
gh pr list --repo <owner>/<repo> --state open \
--json number,headRefName,milestone,isDraft,title \
--jq '.[] | select(.milestone.title == "<title>")'
- Exactly one open PR with that milestone → use it.
- More than one → ask the user which to ship.
- Zero → suggest
/next-issue(no work has landed yet) and abort.
If --pr <N> is passed, fetch that PR and verify its milestone matches.
Readiness checklist (pre-merge)
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.
- 14d ago Changed · +19 lines 29b66738cbb5
- 1mo ago Changed · -57 tokens per session b4a027133ac1
- 1mo ago First seen · 245 lines · 105 tokens per session scan A bba95ab18443
ship is a skill published in the GitHub repository stefan-jansen/coding-agent-toolkit (33 stars, last pushed yesterday), licensed MIT. It adds 48 tokens to every session and 2,846 once invoked, about $0.0002 per session on Opus 5.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.
release
Fully automate a release with version-bump and childhood.
release-notes
Generate user-facing release notes from tickets, PRDs, or changelogs. Creates clear, engaging summaries organized by category (new features, improvements, fixes). Use when writing release notes, creating changelogs, announcing product updates, or summarizing what shipped.
multi-agent-release-manager
Cleans up the workspace, formats code, runs presubmit checks, and uploads CLs to Gerrit.
pack-submit
Package one of this agent's own skills as a standalone community pack and submit it to the aeon registry as a PR.
release-helper
Ensures configuration and code changes are released correctly. Use PROACTIVELY whenever you edit config.json, change any setting, or fix a configuration bug in this project, so the change reaches production.