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 renanflustosa/octo-cluster --skill shipgit clone --depth 1 https://github.com/renanflustosa/octo-clusterWrote 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/renanflustosa/octo-cluster/ship)<a href="https://agentmods.dev/skills/renanflustosa/octo-cluster/ship"><img src="https://agentmods.dev/badge/skills/renanflustosa/octo-cluster/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/renanflustosa/octo-cluster/ship"><img src="https://agentmods.dev/badge/skills/renanflustosa/octo-cluster/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.00034 | $0.01716 |
| Opus 5.5 | $0.00014 | $0.00686 |
| Sonnet 5.5 | $0.00007 | $0.00343 |
| Haiku 4.5 | $0.00003 | $0.00172 |
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 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.
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 — 143 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ship
Ship the working tree of the repo in the session's working directory: inspect → understand → split logically → validate → commit → pick strategy → push/PR → verify → report. /ship is not "commit everything and push".
Notes: $ARGUMENTS
Octo root (holds the script): !pwsh -NoProfile -Command '$d = Get-Item "${CLAUDE_SKILL_DIR}"; if ($d.Target) { $d = Get-Item ([string]$d.Target) }; (Resolve-Path (Join-Path $d.FullName "../../..")).Path'
If plan mode is on, stop: say that /ship needs plan mode off (Shift+Tab) and end. Work autonomously; ask only on the stop conditions below.
1. Inspect (read-only)
From the repo root: git status --short --branch, git diff --stat, git diff --cached --stat, git log --oneline -10, git remote -v, then:
pwsh -NoProfile -ExecutionPolicy Bypass -File <octo>/scripts/ship.ps1 -WhatIf
It fetches origin/main and prints the branch, ahead/behind vs origin/main, the origin default branch, commits already ahead, and the delivery mode with its reason (config, GitHub branch protection or rulesets, or unknown). It modifies nothing.
Stop (SHIP BLOCKED) when the state is ambiguous: merge/rebase/cherry-pick in progress, HEAD diverged from origin/main, the origin default branch is not main, or commits already ahead of origin/main that are not clearly part of this work. On another branch with no commits of its own, git switch main is a safe move (it carries the working tree).
2. Split into logical commits
Read the actual diffs (git diff, and the content of untracked files). Group changes into independently understandable commits: one logical change each (feat, fix, refactor, test, docs, chore, build). Never one giant commit because many files changed; never squash logical changes to cut the count; unrelated changes go in separate commits.
- A file with unrelated hunks → partial staging.
git add -pis interactive and unavailable: write the hunks to a patch in the scratchpad andgit apply --cached <patch>, then confirm withgit diff --cached. - Do not edit source to make commits cleaner. Preserve all user work: no
stash,reset --hard,checkout --,restoreorcleanon user files. - Changes outside the session's work that you cannot attribute: leave them uncommitted and list them in the report.
- Never stage
.env*, private keys, tokens, credential stores,state/, logs, or large generated artifacts. A diff containing credential-like values → stop withSHIP BLOCKEDnaming the file and line, never the value.
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 Changed · +71 lines · +11 tokens per session 76fa10eae719
- 4d ago Changed · +32 lines · +1 tokens per session 531d9a156037
- 14d ago First seen · 40 lines · 22 tokens per session scan A 77a2fb6d59a2
ship is a skill published in the GitHub repository renanflustosa/octo-cluster (4 stars, last pushed 3d ago), licensed MIT. It adds 34 tokens to every session and 1,716 once invoked, about $0.0001 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-09-16.
Other skills, from other repositories
contextual-commit
Write contextual commits that capture intent, decisions, and constraints alongside code changes. Use when committing code, finishing a task, or when the user asks to commit. Extends Conventional Commits with structured action lines in the commit body that preserve WHY code was written, not just WHAT changed.
resolve-publish
Commit the validated fix and follow local-only, workflow-owned, or direct PR publication.
work-unit-commits
Plan commits as reviewable work units. Trigger: implementation, commit splitting, chained PRs, or keeping tests and docs with code.
ijfw-commit
Terse conventional commits. Trigger: commit, git commit, /ijfw-commit.
github-commenting
How to post clean, rich, deduplicated GitHub PR review comments — suggestion blocks, multi-line anchors, markers, formatting rules. Load before posting or fixing any PR comment.
cross-repo-cache
Check if cross-repo coordinator results can be reused, avoiding redundant Sonnet agent launches. Compares peer repo git hashes against stored hashes from last coordinator run. Triggers on: entering Phase 1.4.1, checking cross-repo cache, before discovering peers. Returns CROSSREPOCACHEHIT with cached status or…