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 nicodiansk/turbocharge --skill shipgit clone --depth 1 https://github.com/nicodiansk/turbochargeWrote 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/nicodiansk/turbocharge/ship)<a href="https://agentmods.dev/skills/nicodiansk/turbocharge/ship"><img src="https://agentmods.dev/badge/skills/nicodiansk/turbocharge/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/nicodiansk/turbocharge/ship"><img src="https://agentmods.dev/badge/skills/nicodiansk/turbocharge/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.00076 | $0.01170 |
| Opus 5.5 | $0.00030 | $0.00468 |
| Sonnet 5.5 | $0.00015 | $0.00234 |
| Haiku 4.5 | $0.00008 | $0.00117 |
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 9d 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 — 113 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ship
Complete development work by verifying tests and presenting integration options.
Announce: "Using ship to finalize this work."
Routing. If the request is to triage review comments (in a file or pasted into the conversation), run Step 1 (tests), then go straight to Triage review comments and skip the menu. If it names only a PR, ask the user to save its comments to a file or paste them. To watch a PR's checks and comments instead, Claude Code has /autofix-pr.
Step 1: Verify Tests
# Run project's test suite
npm test / cargo test / pytest / go test ./...
If tests fail: Stop. Show failures. Cannot proceed. If tests pass: Continue.
Step 2: Determine Base Branch
git merge-base HEAD main 2>/dev/null || git merge-base HEAD develop 2>/dev/null || git merge-base HEAD master 2>/dev/null
Step 3: Present Options
Implementation complete. What would you like to do?
1. Merge back to <base-branch> locally
2. Push and create a Pull Request
3. Keep the branch as-is (I'll handle it later)
Which option?
Present the menu exactly as written. Discarding the work is not an option on it: it happens only when the user explicitly asks (see below).
The menu waits for the user's pick, even when Claude invoked ship on its own. Never merge (Option 1) or discard unless the user picked it or asked for it in this conversation.
Step 4: Execute Choice
Option 1: Merge Locally
git checkout <base-branch>
git pull
git merge <feature-branch>
# Verify tests on merged result
git branch -d <feature-branch>
Option 2: Push and Create PR
git push -u origin <feature-branch>
gh pr create --title "<title>" --body "$(cat <<'EOF'
## Summary
<2-3 bullets>
## Test Plan
- [ ] <verification steps>
EOF
)"
Option 3: Keep As-Is
Report: "Keeping branch. Worktree preserved at ."
Discard (only on explicit request)
Only when the user explicitly asks to throw the work away. Require typed "discard" confirmation: list the branch and its commits that will be deleted, and wait for the exact word discard. "Yeah, get rid of it" is not the confirmation. Then:
git checkout <base-branch>
git branch -D <feature-branch>
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.
- 9d ago Changed · -39 lines · -31 tokens per session 10847a753b6c
- 10d ago Changed · +62 lines · +61 tokens per session c678c1b775ed
- 12d ago Changed · +1 lines · +8 tokens per session c5b0f9e084da
- 1mo ago First seen · 89 lines · 38 tokens per session scan A 29c54a9066f2
ship is a skill published in the GitHub repository nicodiansk/turbocharge (3 stars, last pushed 7d ago), licensed MIT. It adds 76 tokens to every session and 1,170 once invoked, about $0.0003 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-31.
Other skills, from other repositories
standup
Facilitate a read-only standup across git worktrees, branches, or PRs to compare changes and produce one consolidation plan.
version-bump
Automated semantic versioning and release workflow for Claude Code plugins. Handles version increments across package.json, marketplace.json, plugin.json manifests, build verification, git tagging, GitHub releases, and changelog generation. npm publishing is done by the tag-triggered GitHub Actions workflow through…
babysit
Watch a pull request or review cycle until it is ready to merge. Use when asked to babysit, monitor, or keep checking PR comments, reviews, and CI until all actionable issues are resolved.
childhood
Babysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release.
build-and-release
Fully automate building and releasing a coding task.
release
Fully automate a release with version-bump and childhood.