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/appsvortex/arness/arn-shippingnpx skills add AppsVortex/arness --skill arn-shippinggit clone --depth 1 https://github.com/AppsVortex/arnessWhat 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.00126 | $0.00546 |
| Opus 5 | $0.00063 | $0.00273 |
| Sonnet 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 2d 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.
- 2d 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 1mo ago), licensed MIT. It adds 126 tokens to every session and 546 once invoked, about $0.0006 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-30.
Other skills, from other repositories
git-workflow-and-versioning
Structures git workflow practices. Use when making any code change. Use when committing, branching, resolving conflicts, opening or reviewing a pull request (PR), pushing to a remote, or when you need to organize work across multiple parallel streams. Use when cutting a release, choosing a semantic version bump…
ship
Build, commit, push & version bump workflow - automates the complete release cycle.
ce-commit-push-pr
Commit, push, and open a PR. Use when asked to ship/open a PR, or for PR-description-only flows like writing, rewriting, or describing a PR body.
release
Create a new es-toolkit release (version bump, changelog, tag).
git-workflow
安全处理 Git 状态检查、提交信息、commit、分支、push、PR 和 rebase。用于用户要求检查改动、生成或创建提交、管理分支、推送、发起 PR 或整理历史时；严格区分每个动作的授权，并保护工作树中已有和无关的修改。.
zed-cherry-pick
Cherry-pick one or more merged PRs and/or commits into Zed's preview or stable release branch. Use this whenever the user mentions cherry-picking to preview/stable, a failed cherry-pick run, or wants to manually port fix(es) into a release branch.