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.
git 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/commands/renanflustosa/octo-cluster/ship)<a href="https://agentmods.dev/commands/renanflustosa/octo-cluster/ship"><img src="https://agentmods.dev/badge/commands/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/commands/renanflustosa/octo-cluster/ship"><img src="https://agentmods.dev/badge/commands/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.00000 | $0.00281 |
| Opus 5 | $0.00000 | $0.00140 |
| Sonnet 5 | $0.00000 | $0.00056 |
| Haiku 4.5 | $0.00000 | $0.00028 |
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 10d 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.
What it actually says
ship
Agent mode. Verify, then deliver via scripts/ship.ps1 (repo-agnostic).
Run:
pwsh -NoProfile -ExecutionPolicy Bypass -File scripts/ship.ps1 -CommitMessage "fix: short conventional summary"
pwsh -NoProfile -ExecutionPolicy Bypass -File scripts/ship.ps1 -WhatIf
Delivery mode (auto-detected):
| Protections | Action |
|---|---|
| None | Commit + push direct to main |
| Any detected | Temp branch ship/<timestamp> + PR to main |
Protection signals: scripts/boundary-audit.ps1, git hooks referencing audit/gate, remote branch protection (best-effort via gh), or .ship.yaml / .ship.json with mode: pr or protections: true. Override with mode: direct in config.
Rules:
- Conventional commit summary (
feat:,fix:,chore:, ...). - Do not run git by hand during ship — let the script do it.
- If boundary-audit exists and fails, fix and re-run.
- PR mode requires
ghCLI.
Verdict: READY | NEEDS FIXES — report result in <=5 lines.
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.
- 10d ago First seen · 29 lines · 0 tokens per session scan A cd3447870fc1
ship is a command published in the GitHub repository renanflustosa/octo-cluster (4 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 281 tokens. 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 commands, from other repositories
ijfw-ship
Run the IJFW workflow Ship phase (Deep D6). Pre-flight, deploy, and close. Usage: /ijfw-ship.
update-documentation
You are a release engineer responsible for maintaining the root-level CHANGELOG.md and verifying plugin READMEs. Analyze git changes, update the single CHANGELOG.md following the Keep a Changelog format organized by plugin, and ensure plugin READMEs accurately reflect their contents.
fire-update
Check for and apply plugin updates from GitHub repository.
ship
Pre-ship pipeline — test, review, then prepare a clean commit.
queue
"What's coming up — plan steps, releases, backlog, and overdue decisions?".
reqforge-greenkeeper
Diagnose and fix ReqForge repository release gate failures.