Borrowing it
Nothing to install: this file belongs to arcasilesgroup/ai-engineering. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/arcasilesgroup/ai-engineering/main/.agents/skills/ai-ship/SKILL.mdgit clone --depth 1 https://github.com/arcasilesgroup/ai-engineeringWrote 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/arcasilesgroup/ai-engineering/ai-ship)<a href="https://agentmods.dev/skills/arcasilesgroup/ai-engineering/ai-ship"><img src="https://agentmods.dev/badge/skills/arcasilesgroup/ai-engineering/ai-ship.svg" alt="Measured on agentmods" 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.00122 | $0.00854 |
| Opus 5 | $0.00061 | $0.00427 |
| Sonnet 5 | $0.00024 | $0.00171 |
| Haiku 4.5 | $0.00012 | $0.00085 |
Grade A, and why
ai-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 8d 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 — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Land the work
What it produces
Commits, a changelog entry, a pull request on origin/<branch>, and a branch that gets deleted after it merges.
Steps
- Run the repository's own gate — the recipe set CI runs, whatever it is called here — and show its output. Not a summary of it — the output. If it is red, stop here; nothing below this line is worth doing.
- Commit in the shape the change actually has: one commit, one change. A commit that
needs the word "and" in its subject is two commits. Subject is
<type>(<scope>): <what changed>, imperative, and the body says why rather than what. Never--no-verify: the hooks are the floor, and what they would have said is the thing that needs fixing. - Update the changelog. A breaking change is written as a breaking change, in the words somebody upgrading would search for.
- Tick the production-ready boxes in the spec. Assertion 19 reads what is beside each
tick, so a box with no command in backticks and no
not applicablefails the gate. - Open the pull request. The first paragraph is what changed, in plain words, for somebody who does not code. Then the spec link, then what to look at first, then what you are not confident about — that last section is the one reviewers use most.
- If the spec's frontmatter has a
ref, append the closing keyword to the body:Closes owner/repo#45on GitHub,Fixes #45on Azure Repos,AB#45where the Azure Boards app bridges the two. One constraint catches people: the pull request must target the default branch, or the keyword is ignored and nothing is linked or closed. - After it merges, delete the branch, and say in one line what is now true that was not true before.
- A conflict is resolved by intent and never by taking a side. Read what each side was
trying to do, say it in the merge in one line each, and keep the change that serves both
— or stop and ask, because a conflict resolved by whoever pushed last is a decision
nobody took.
/ai-debugowns finding the cause when the merged result then misbehaves.
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.
- 8d ago First seen · 63 lines · 122 tokens per session scan A f0543ef9bcff
ai-ship is a skill published in the GitHub repository arcasilesgroup/ai-engineering (54 stars, last pushed 7d ago), licensed Apache-2.0. It adds 122 tokens to every session and 854 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
Use this skill for anything related to Git and version control workflows. Trigger when the developer asks for help with commit messages, PR descriptions, pull request reviews, branching strategies, changelog generation, release notes, code review etiquette, or Git conventions. Keywords: commit, PR, pull request…
github-operations
WORKFLOW SKILL — Full GitHub contribution lifecycle: branches, conventional commits, issues, PRs, Actions, releases. gh CLI-first with MCP fallback. WHEN: "commit", "push", "open PR", "create branch", "create issue", "cut release", "GitHub operation". DO NOT USE FOR: Azure infrastructure, Bicep/Terraform code…
git-commit-push-pr
Commit, push, and create a PR. Prompts for branch and PR target using quick multi-choice questions. Lightweight alternative to /workflow-ship without preflight checks.
brpr
(devtools plugin) Create a branch, commit changes, push, and open a PR — or just commit+push+PR if already on a feature branch. Links related issues from GitHub or Linear based on project tracker config.
plate
Turn finished local work into a commit, an ordinary pull request, or a pull request stack. Use this skill to commit changes or to publish a branch. Use it to open or update a pull request. Use it to create, sync, restack, or submit a pull request stack. You can also run /plate. This skill owns all staging, commits…
ag-versionar-codigo
Gerencia git - branches, commits semanticos, PRs, releases e changelog. Use ao final de cada fase ou feature para manter historico limpo.