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 akka/ai-marketplace --skill shipgit clone --depth 1 https://github.com/akka/ai-marketplaceWrote 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/akka/ai-marketplace/ship)<a href="https://agentmods.dev/skills/akka/ai-marketplace/ship"><img src="https://agentmods.dev/badge/skills/akka/ai-marketplace/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/akka/ai-marketplace/ship"><img src="https://agentmods.dev/badge/skills/akka/ai-marketplace/ship.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.00035 | $0.01156 |
| Opus 5 | $0.00017 | $0.00578 |
| Sonnet 5 | $0.00007 | $0.00231 |
| Haiku 4.5 | $0.00003 | $0.00116 |
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 10d 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 — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.
User Input
You MUST consider the user input before proceeding.
Purpose
/akka:ship runs the auditors for every applicable exit condition in scope for
the requested ship target, and on pass runs the ship steps the organization
declared for that target. The target argument is REQUIRED. Two targets are
accepted:
review— runs the auditors for every applicable exit condition taggedauthororreview. On pass, runs the organization's review ship steps (typically push the branch and open a pull request).release— runs the auditors for every applicable exit condition at any tier (author,review, andrelease). On pass, runs the organization's release ship steps (typically deploy to production).
Author-time is a precondition, not a ship target. There is no /akka:ship author.
The author-time conditions are evaluated first, on their own, before any higher-tier auditor is given a chance. In À la carte mode the gate is advisory like every other condition: the run continues, every in-scope tier is evaluated, and the user gets the complete picture to override against.
In Enforced mode a ship that fails them stops right there — the review-time and release-time checks never run, so a ship that cannot succeed does not first spend minutes on scanning, dynamic analysis, or live-service probes. The user sees only the author-time verdict, which is the only one that has been computed.
An active waiver satisfies the precondition exactly as it satisfies any other condition — a waiver is a person's time-bound, recorded acceptance, not a bypass.
Outline
-
Parse the target from
the user's request. Read the first argument. It MUST berevieworrelease. If missing, invalid, or anything else, stop and tell the user: "/akka:shiprequires an explicit target:revieworrelease. For example:/akka:ship review." Do not call the CLI. -
Invoke the CLI. Run
akka specify ship <target>in the project directory (via the shell). Capture the output. The CLI:- Runs the author-time auditors first; in Enforced mode stops there if any of them blocks.
- Otherwise runs the auditors for every remaining applicable exit condition in scope for the target.
- Reports the verdict (
READY_TO_SHIPorNOT_READY). - In À la carte mode, records an explicit override and proceeds even when
the verdict is
NOT_READY. - In Enforced mode, refuses to run any ship steps unless the verdict is
READY_TO_SHIP. - Writes a conformance receipt recording which target was shipped, what was
verified, and any conditions that remained
openwith their reasons.
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.
- 10d ago First seen · 102 lines · 35 tokens per session scan A e18fea658a54
ship is a skill published in the GitHub repository akka/ai-marketplace (6 stars, last pushed 2d ago), licensed Apache-2.0. It adds 35 tokens to every session and 1,156 once invoked, about $0.0002 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-31.
Other skills, from other repositories
gsd-complete-milestone
Archive completed milestone and prepare for next version.
release-archivist
Close out a spec-superflow change with verification, summary, and archive readiness. Invoke when implementation is complete, verification is underway, or the user asks for a final wrap-up.
codex-issue-coordinator
Coordinates a large batch of GitHub issues through separate Codex worker threads, tested pull requests, review loops, and gated merges. Use when the user asks one Codex thread to manage several coding sessions or complete a parent issue, milestone, or issue batch.
exit-strategy
Use when implementation is complete and all tests pass — guides the clean exit from a development branch with structured options for merge, PR, or cleanup.
release
A skill for publishing a new prospec GitHub release by updating version strings, creating a tag, and writing release notes.
submit-pr
A skill for opening a pull request in the prospec project's required format after a change is completed and archived.