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/mgiovani/cc-arsenal/shipnpx skills add mgiovani/cc-arsenal --skill shipgit clone --depth 1 https://github.com/mgiovani/cc-arsenalWrote 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/mgiovani/cc-arsenal/ship)<a href="https://agentmods.dev/skills/mgiovani/cc-arsenal/ship"><img src="https://agentmods.dev/badge/skills/mgiovani/cc-arsenal/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.1 | $0.00210 | $0.02408 |
| Opus 5 | $0.00105 | $0.01204 |
| Sonnet 5 | $0.00042 | $0.00482 |
| Haiku 4.5 | $0.00021 | $0.00241 |
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 6d 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 — 155 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ship
Take the current branch from "code done" to "merged" in one pass. This is a thin orchestrator: every step delegates to the sibling skill that already owns that logic. Do not re-implement review rules, commit conventions, or PR templates here: invoke the skill.
Pipeline integrity
Every stage's reported result must quote the actual command you ran and its actual exit status or output. A stage you did not run is reported as SKIPPED: , never as passed, never estimated, never inferred from a similar-looking earlier run. The whole value of a ship train is that green means green; one fabricated gate poisons every stage after it, because the human trusts stage 6 only because they trust stages 1-5.
The train
Run these in order. Stop at the first red gate and report it, do not skip a step or push through a failure.
| # | Step | How |
|---|---|---|
| 1 | Pre-flight | Confirm there's a diff to ship, working tree state, target base branch |
| 2 | Code review | Invoke the review-code skill on the current diff |
| 3 | Pre-merge checks | Auto-detect and run project checks (tests, lint, visual diff) |
| 4 | Commit | Invoke the git-commit skill's conventions |
| 5 | PR | Invoke the git-create-pr skill's conventions |
| 6 | CI + merge | Watch CI (optional), report or merge on green |
Track progress with TodoWrite (one line per step above) so the user sees where the train is if a gate stops it.
Step 1: Pre-flight
git branch --show-current: refuse to run onmain/master/devdirectly (nothing to ship from a target branch).git status --porcelain: if dirty, useAskUserQuestion(or ask in plain text if that tool isn't available) whether to include the changes or stop.- Determine base branch: use
--baseif given, elsegh repo view --json defaultBranchRef -q .defaultBranchRef.name, elsemain. git log <base>..HEAD --oneline: if empty, there's nothing to ship; stop and say so.
Step 2: Code review
Invoke the review-code skill (via the Skill tool where available, otherwise apply its review dimensions inline) scoped to the diff against the base branch. This is analysis only: it does not touch files.
What ships with it
2 files 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.
- 6d ago First seen · 155 lines · 210 tokens per session scan A c9f19eb976cd
ship is a skill published in the GitHub repository mgiovani/cc-arsenal (7 stars, last pushed 6d ago), licensed MIT. It adds 210 tokens to every session and 2,408 once invoked, about $0.0011 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
ops-demo
CocoOps demo mode activator — populates .cocoplus/ops/demo/ with realistic mock data and sets cocoplus.toml [demo] enabled = true. Invoked via $ops demo.
acl-rule-analysis
Vendor-agnostic ACL and firewall rule analysis with shadowed rule detection, overly permissive rule identification, unused rule discovery, redundant rule flagging, and rule ordering optimization. Covers ACLs (Cisco/JunOS/EOS) and firewall policies (PAN-OS/FortiGate/CheckPoint).
agent-teams-simplify-and-harden
Implementation + audit loop using parallel agent teams with structured simplify, harden, and document passes. Spawns implementation agents to do the work, then audit agents to find complexity, security gaps, and spec deviations, then loops until code compiles cleanly, all tests pass, and auditors find zero issues or…
agent-team-orchestration
Orchestrate multi-agent teams with defined roles, task lifecycles, handoff protocols, and review workflows. Use when: (1) Setting up a team of 2+ agents with different specializations, (2) Defining task routing and lifecycle (inbox → spec → build → review → done), (3) Creating handoff protocols between agents, (4)…
agent-bom-enforce
Enforce security policies on MCP tool calls and block dangerous operations at runtime. Use when: "block risky calls", "apply policy", "proxy", "runtime protection", "policy enforcement", "intercept MCP calls".
diary
Show CocoDiary operator-facing work journal status.