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/jerry0022/dotclaude/shipnpx skills add Jerry0022/dotclaude --skill shipgit clone --depth 1 https://github.com/Jerry0022/dotclaudeWrote 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/jerry0022/dotclaude/ship)<a href="https://agentmods.dev/skills/jerry0022/dotclaude/ship"><img src="https://agentmods.dev/badge/skills/jerry0022/dotclaude/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.00048 | $0.01655 |
| Opus 5 | $0.00024 | $0.00827 |
| Sonnet 5 | $0.00010 | $0.00331 |
| Haiku 4.5 | $0.00005 | $0.00166 |
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 4d 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 — 111 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ship Extension — dotclaude (plugin-source repo)
Adds one project-specific step to /ship: a post-ship self-update of the
installed devops plugin. This repo ships the plugin that runs the ship, so the local
install must be reconciled with what was just merged. See reference.md in this folder
for the full rationale (double-restart problem, observed cache/registry drift).
This extension is additive — every plugin-default step still runs unchanged.
Step 6.5 — Announce the local channel outcome IN the completion card
Do this before calling render_completion_card in Step 6, using pure file reads
(no MCP). Channel-aware (ring model): a plain /ship publishes vNew to the
alpha channel only. The local install follows its channel pin at
~/.claude/plugins/.channels.json ({ "dotclaude": "<channel>" }; absent → stable).
Whether the local install moves to vNew depends on that pin — it does NOT
automatically sync to every ship.
- Read the channel pin:
~/.claude/plugins/.channels.json→dotclaude(absent/unknown →stable). - Read installed version:
~/.claude/plugins/installed_plugins.json→plugins["devops@dotclaude"][0].version. - Add exactly one
userFinalTestitem, in the user's language:- Pin is
alpha— the install tracks alpha, so the Step 8 finalizer moves it to vNew:{ action: "devops lokal (alpha) auf v<vNew> synchronisiert — Claude einmal neu starten, dann ist die neue Version aktiv.", afterDeployment: true } - Pin is
beta/stable(the default) — an alpha-only ship does NOT reach this install. Do not claim any local sync; point to promotion:{ action: "v<vNew> ist auf alpha veröffentlicht; dein <pin>-Install bleibt auf v<installed>. /promote promoten (alpha→<pin>), danach zieht der Install v<vNew> beim nächsten Start.", afterDeployment: true }
- Pin is
Never assert "lokal auf vNew synchronisiert" on a beta/stable pin. The finalizer (Step 8) correctly holds the install on its pinned channel tag, so an alpha-only ship leaves it unchanged — a false "synced" claim sends the user hunting a non-existent sync failure (observed 2026-07-19). This keeps the completion card the last visible output (per plugin Step 6); do not print the notice as separate prose after the card — the card carries it.
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.
- 4d ago First seen · 111 lines · 48 tokens per session scan A 3fa67b381bb6
ship is a skill published in the GitHub repository Jerry0022/dotclaude (5 stars, last pushed today), licensed MIT. It adds 48 tokens to every session and 1,655 once invoked, about $0.0002 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…