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 AbdurRafay2004/handoff --skill shipgit clone --depth 1 https://github.com/AbdurRafay2004/handoffWrote 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/abdurrafay2004/handoff/ship)<a href="https://agentmods.dev/skills/abdurrafay2004/handoff/ship"><img src="https://agentmods.dev/badge/skills/abdurrafay2004/handoff/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/abdurrafay2004/handoff/ship"><img src="https://agentmods.dev/badge/skills/abdurrafay2004/handoff/ship.svg" alt="Reviewed on agentmods" width="80" 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.00105 | $0.02729 |
| Opus 5.5 | $0.00042 | $0.01092 |
| Sonnet 5.5 | $0.00021 | $0.00546 |
| Haiku 4.5 | $0.00011 | $0.00273 |
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 15d 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.
| Config only | `curl -sf <url> -o /dev/null -w "%{http_code}"` — expect 200 | How it starts
The opening of the file, as written. The whole thing — 211 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ship
Part of the Ship phase — see the workflow skill for tiers and sequencing.
Shipping is the phase where mistakes become public and expensive. The rule that governs everything below: every ship step ends with evidence a non-coding PM can judge — a PR URL, green CI, a deploy URL, smoke-check output, a screenshot. Never "deployed, should be fine." Show the thing.
Tier scaling
| Tier | Ship process | Evidence at the end |
|---|---|---|
| T1 | branch → commit → PR → merge. Deploy only if the change is user-visible or the user asks. | PR URL + green CI |
| T2 | T1 + deploy + single-pass smoke check on the live URL. | Deploy URL + smoke output |
| T3 (money/auth/data/migrations) | Full runbook: rollback criteria written BEFORE deploying, staged rollout, post-deploy monitoring, T+24h check. See references/launch-runbook.md. | Runbook with each gate checked + live evidence |
Never enter Ship without a passing Verify phase (verify-done). Shipping does
not re-litigate verification — but it does re-run it when code changes (below).
Git hygiene
- Never
git add -Aorgit add .. Stage only the files you changed for this task, by explicit path. Unrelated dirt in the working tree stays out of your commit — it belongs to another change or to nobody. - Bisectable commits. Group the diff into logical units, one coherent change
per commit (not one file per commit). Order so dependencies land first:
- Infrastructure: config, migrations, route/schema additions
- Data layer and services (with their tests)
- UI: components, pages, styles (with their tests)
- Docs/changelog last A module and its test file travel in the same commit. Each commit must be independently valid — no broken imports, no references to code that doesn't exist yet. Small diffs (<50 lines across <4 files) can be a single commit.
- Every commit revertible.
git revert <sha>on any single commit should cleanly undo one logical change. If a schema change and dependent code can't be reverted independently, note that in the commit body — it changes the rollback plan. - Never force push. Never rewrite pushed history. Plain
git pushonly. Sole exception: scrubbing a leaked secret from history (seesecurity), with the user's explicit approval — rotate the secret first.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 15d ago Changed c19158c107fb
- 1mo ago First seen · 211 lines · 105 tokens per session scan A 18871f7c9c0b
ship is a skill published in the GitHub repository AbdurRafay2004/handoff (4 stars, last pushed 10d ago), licensed MIT. It adds 105 tokens to every session and 2,729 once invoked, about $0.0004 per session on Opus 5.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
update
Safe cc10x upgrade through the Claude Code plugin CLI. Lists every installed scope, refreshes the marketplace, updates each scope, and optionally carries local patches over to the new install. Use this skill when: updating cc10x, upgrading, pulling latest cc10x, syncing plugin, refreshing cache, or checking for new…
release
Release a new version of the mumei repository. Invoke when the user gives an explicit release instruction ("release it", "/release", "patch release", "ship 0.2.0"). Takes no argument or "patch" / "minor" / "major" for a SemVer bump, or a direct version such as "0.2.0". Wraps any uncommitted changes into a single…
ship
Finish a development branch once the tests pass — merge locally, push and open a pull request, keep it, or discard it. Use when the work is done and the user asks to merge, open the PR, wrap up or clean up the branch. Not for checking the code first; see /development:review.
release
Cut a brooks-lint release: set the version in package.json, propagate it across all four plugin manifests and every version-bearing text file (README badges, docs site metadata), write the CHANGELOG entry, validate, then commit, push, tag, and publish the GitHub release. Triggers when the maintainer asks to "release"…
release
CONTRIBUTOR TOOL - Cut a plugin release: bump plugin.json version, finalize CHANGELOG, update README if needed, gate on make ci, commit, tag vX.Y.Z, and create the GitHub release. Use when shipping a new plugin version. NOT distributed.
ops-release
OPS on-demand: This skill should be used when the user asks to "release the plugin", "publish ops…