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 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/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/mgiovani/cc-arsenal/ship"><img src="https://agentmods.dev/badge/skills/mgiovani/cc-arsenal/ship.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.02537 |
| Opus 5.5 | $0.00084 | $0.01015 |
| Sonnet 5.5 | $0.00042 | $0.00507 |
| Haiku 4.5 | $0.00021 | $0.00254 |
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 22d 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 — 160 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
Copy this checklist, tick each step as it passes, and follow the gates. Stop at the first gate that exhausts its rounds and report it; do not skip a step or push through a failure.
- [ ] 1. Pre-flight: a diff exists, working tree state known, base branch chosen
- [ ] 2. Code review (review-code on the diff vs base)
Critical/High finding: fix it (or user accepts the risk), then re-run step 2
- [ ] 3. Pre-merge checks (auto-detected project gates)
Any check red: fix it, then re-run step 3
- [ ] 4. Commit (git-commit conventions)
- [ ] 5. PR (git-create-pr conventions)
- [ ] 6. CI + merge (optional)
CI red: fix, return to step 3 to re-run local checks, then push and re-watch
Cap: 3 fix rounds per gate, then stop and report what still fails
Each step's details are in its section below. TodoWrite can hold the same lines 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.- Requires
gh(brew install gh): confirmgh auth statussucceeds, else stop and tell the user to rungh auth login. - 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.
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.
- 22d ago Changed · +4 lines 70f9c479b30e
- 1mo ago Changed · +1 lines 9a1b0faf1d85
- 1mo ago First seen · 155 lines · 210 tokens per session scan A c9f19eb976cd
ship is a skill published in the GitHub repository mgiovani/cc-arsenal (8 stars, last pushed 2d ago), licensed MIT. It adds 210 tokens to every session and 2,537 once invoked, about $0.0008 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
gitlab
Agent-callable GitLab tools — manage issues and merge requests, review diffs, commit files, run pipelines, and search. Use when the user mentions GitLab or wants to review or merge an MR, commit code, run CI, or manage issues — even if they don't name GitLab explicitly.
repo-hygiene
Use when the scheduled repo-hygiene workflow runs from GitHub Actions (or an operator dry-run) to scan the repository for small, certain docs/test/code hygiene issues and fix them as one batched branch.
gh-skill
Manage agent skills with gh skill. Use this skill to discover, preview, install, update, and publish Agent Skills so an agent can self-manage the skills available in its environment.
cw-gates
Use before claiming any Codewhale change is done, green, or ready to land: the focused-to-broad verification ladder, the budget checks CI enforces, and the rules for what counts as a passing test.
atmos-hooks
Atmos hooks: lifecycle events, hook kinds, command/store/git/security hooks, step/steps hooks, when: conditions, scoping and overrides, toolchain integration, --skip-hooks, and Atmos Pro/local output.
conventional-commit
Conventional Commit - Generate Conventional Commits 1.0.0 compliant messages. MANDATORY for all git commits. Invoke when user says 'commit', 'commit this', or asks to commit code.