Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add AppsVortex/arness/plugin install arn-codeWrote 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/appsvortex/arness/arn-shipping)<a href="https://agentmods.dev/skills/appsvortex/arness/arn-shipping"><img src="https://agentmods.dev/badge/skills/appsvortex/arness/arn-shipping/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/appsvortex/arness/arn-shipping"><img src="https://agentmods.dev/badge/skills/appsvortex/arness/arn-shipping.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.00126 | $0.00546 |
| Opus 5.5 | $0.00050 | $0.00218 |
| Sonnet 5.5 | $0.00025 | $0.00109 |
| Haiku 4.5 | $0.00013 | $0.00055 |
Grade A, and why
arn-shipping 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 1mo 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
Arness Shipping
Commit, push, and optionally create a pull request. This is a first-citizen entry point that wraps arn-code-ship and provides chaining context to the next stage (arn-reviewing-pr).
This skill is a thin orchestration wrapper. It MUST NOT duplicate arn-code-ship logic. All shipping work is done by the invoked skill. Arness-shipping handles: prerequisite checks, invoking the ship skill, and informing the user about the next stage.
Step 0: Ensure Configuration
Read ${CLAUDE_PLUGIN_ROOT}/skills/arn-code-ensure-config/references/step-0-fast-path.md and follow its instructions. This guarantees a user profile exists and ## Arness is configured with Arness Code fields before proceeding.
Workflow
Step 1: Invoke Ship
Show progress:
Shipping: SHIP (branch -> stage -> commit -> push -> PR)
^^^^
Invoke the ship skill:
Skill: arn-code:arn-code-ship
The ship skill handles all internal decisions: branching, staging, commit message generation, pushing, and PR creation. It has its own user interactions. Wait for it to complete.
Step 2: Completion Handoff
After arn-code-ship completes, present the chain exit:
"When your PR gets review feedback, run /arn-reviewing-pr to validate and address comments."
Error Handling
## Arnessconfig missing: Handled by Step 0 (ensure-config) — this should not occur if Step 0 completed successfully.arn-code-shipfails: Present the error. Ask: retry or abort.- Nothing to ship (clean tree, no commits ahead):
arn-code-shiphandles this internally — it will inform the user. No action needed at this level.
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.
- 1mo ago First seen · 56 lines · 126 tokens per session scan A 2e3b62165430
arn-shipping is a skill published in the GitHub repository AppsVortex/arness (33 stars, last pushed 2mo ago), licensed MIT. It adds 126 tokens to every session and 546 once invoked, about $0.0005 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-30.
Other skills, from other repositories
release
Bump a plugin's version, write a detailed changelog entry for the upgrade skill to consume, and commit+push. Takes a plugin slug argument identifying which plugin under plugins/ to release. Use this skill whenever the user says "release", "version bump", "cut a release", "changelog and push", or finishes a set of…
git-branchless
Use when asked for multi-commit stack edits, rebases, fixups, or stacked-PR publishing with branchless git idioms. Not for plain-git workflows in repos without branchless.
handoff
Ship completed work: verify locally, commit related changes, push, create or update the PR, watch CI/reviews, and fix until merge-ready or escalated. Use for "ship it", "create PR", "handoff", or finished code needing delivery.
git-flow
Use when creating a branch, using worktrees for parallel work, committing, or wrapping up. Covers branch naming, conventional commits, short-lived branches, worktree isolation, and final merge/cleanup.
ship
Use after audit returns Verdict PASS. Atomic git commit + ledger update; only the evolve release path makes a tag. Single-writer; cannot fan-out.
git-pr-strategy
Apply safe branching, commits, conflict resolution, review ownership, merge, rollback, and release-tag rules.