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-code-shipnpx skills add AppsVortex/arness --skill arn-code-shipgit 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.00133 | $0.04223 |
| Opus 5 | $0.00067 | $0.02112 |
| Sonnet 5 | $0.00027 | $0.00845 |
| Haiku 4.5 | $0.00013 | $0.00422 |
Grade A, and why
arn-code-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 yesterday.
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 — 276 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Arness Ship
Guides through branching, staging, committing, pushing, and optionally opening a pull request. Works standalone or as the final step in the Arness pipeline.
Pipeline position:
arn-code-review-implementation -> arn-code-document-project -> **arn-code-ship**
This skill handles the entire shipping workflow: verifying git state, ensuring the user is on the right branch, staging changes safely, generating meaningful commit messages, pushing, and creating a pull request via the GitHub CLI or Bitbucket CLI.
Workflow
Step 1: Check Git State
Check ## Arness config in CLAUDE.md for Git: yes. If not present, run runtime check: git rev-parse --is-inside-work-tree.
If Git is not available, inform the user: "This project is not a git repository. /arn-code-ship requires Git." and exit.
Read the Platform field from ## Arness config in CLAUDE.md (values: github, bitbucket, or none). Store this value for use in Step 5. If the Platform field is not present, fall back to legacy detection: check for GitHub: yes and treat as github; otherwise treat as none.
Gather current state:
- Current branch:
git branch --show-current - Uncommitted changes:
git status --short(never use-uall) - Commits ahead of main:
git log main..HEAD --oneline(skip if on main) - Remote tracking:
git rev-parse --abbrev-ref @{upstream}(may fail if no upstream)
If no uncommitted changes AND no commits ahead of remote, inform the user: "Nothing to ship — working tree is clean and up to date with remote." and exit.
Step 2: Branch Decision
If on main/master:
- Warn the user: "You're on the main branch. It's recommended to create a feature branch before shipping."
- Offer to create a new branch:
- If Arness context is available (current spec or plan), suggest a name derived from it (e.g.,
feat/websocket-support,fix/checkout-500-error) - Otherwise ask the user for a branch name
- Create with
git checkout -b <branch-name>
- If Arness context is available (current spec or plan), suggest a name derived from it (e.g.,
- Let the user continue on main if they prefer
What ships with it
1 file 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.
- yesterday First seen · 276 lines · 133 tokens per session scan A 730f2af445c2
arn-code-ship is a skill published in the GitHub repository AppsVortex/arness (33 stars, last pushed 1mo ago), licensed MIT. It adds 133 tokens to every session and 4,223 once invoked, about $0.0007 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
agent-framework-azure-ai-py
Build persistent agents on Azure AI Foundry using the Microsoft Agent Framework Python SDK.
agentmail
Email infrastructure for AI agents. Create accounts, send/receive emails, manage webhooks, and check karma balance via the AgentMail API.
aria
Designs the data model, API contracts, and structural foundation of the system.
luna
Reviews code for objective correctness, security, and reliability.
max
Cleans up and improves existing code without changing behavior.
agent-self-scheduling
Schedule AI agent runs with cron, loops, or external clocks while avoiding unsafe tight autonomous timers.