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 commands/higoralves/orc/shipgit clone --depth 1 https://github.com/HigorAlves/orcWrote 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/higoralves/orc/ship)<a href="https://agentmods.dev/commands/higoralves/orc/ship"><img src="https://agentmods.dev/badge/commands/higoralves/orc/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.00047 | $0.02954 |
| Opus 5 | $0.00023 | $0.01477 |
| Sonnet 5 | $0.00009 | $0.00591 |
| Haiku 4.5 | $0.00005 | $0.00295 |
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 — 198 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/orc:ship
You're done implementing. Time to integrate. This command runs the structured branch-completion flow.
Arguments
-
--auto[=guided|full]— autopilot level for this run (overridesinteraction_policy; taxonomy inorc:using-orc). Soft-inward gates consult the resolved policy —guidedauto-advances mechanical confirms with a printed one-liner;fullpre-approves them from settled decisions (orc:state-protocol), stopping only on escalation-only conditions. Hard-outward gates are unaffected at every level. -
--draft— open the PR as a draft. -
--base <branch>— target a non-default base (e.g.develop,release/v2). -
--verbose— compose the PR body with the long-form template documented in Phase 4. Default is terse, signal-only composition viaorc:caveman-pr. (--cavemanis accepted as a deprecated no-op alias of the default.) -
--max-loc <N>— override the per-PR LOC budget enforced by Phase 4.5 (default: 300, configurable via$ORC_PR_LOC_BUDGETor<repo_root>/.orc/pr-budget.json#budget). Seeorc:pr-size-budget. -
--no-size-gate— bypass Phase 4.5 entirely. Use for emergency hot-fixes where review-cycle time dominates. Records nothing in the PR body.
Workflow
Phase 0 — Detect context
!orc-workspace-detect --banner
Context is injected above (ORC_* vars are exported for any Bash you run — do not re-run detection).
In workspace mode, resolve targetRepos from flags or via AskUserQuestion. Default in workspace mode is to ship every repo in the active workspace session's repos array (orc-state get --field repos — read-for-data per orc:state-protocol). Iron rule: no silent broadcast — confirm before opening multiple PRs.
Phase 1 — Pre-ship verification
Invoke orc:verification-before-completion. Confirm:
- Tests pass.
- Lint / type-check pass (if configured).
- No staged-but-uncommitted changes (
git status --porcelain). - Current branch is NOT a protected branch.
If any check fails, stop and show the failure. Do not proceed.
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 First seen · 198 lines · 47 tokens per session scan A c4ae08557ac9
ship is a command published in the GitHub repository HigorAlves/orc (6 stars, last pushed 7d ago), licensed MIT. It adds 47 tokens to every session and 2,954 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 commands, from other repositories
convert
Use when the user attaches a bank statement PDF or asks for CSV/XLSX/QBO/Xero export of a converted statement. Do not use for spending analysis, reconciliation, or benchmark scoring — those have their own skills.
reconcile
Use when the user asks to check statement coverage, missing periods, balance continuity, or cross-account transfers. Do not use for converting a new PDF, spending categorization, or benchmark scoring.
analyze
Use when the user asks to categorize spending, group by merchant or category, rank top merchants, or show monthly trends on converted statements. Do not use for first-time PDF conversion, period reconciliation, or benchmark scoring.
pn-audit-performance-fe
Surgical frontend performance audit — Core Web Vitals, bundle size, image optimization, render-blocking resources, and page-type budgets. Standalone or chained by pn-frontend-audit.
value
Get the current market value of a vehicle using the VIN provided in $ARGUMENTS.
dispatcher
Pick the next-best repo to work on across the portfolio — rank free repos, recommend one, claim its lease atomically, and route to the entry command.