Borrowing it
Nothing to install: this file belongs to Smana/cloud-native-ref. 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/Smana/cloud-native-ref/main/.agents/skills/ship-it/SKILL.mdgit clone --depth 1 https://github.com/Smana/cloud-native-refWrote 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/smana/cloud-native-ref/ship-it)<a href="https://agentmods.dev/skills/smana/cloud-native-ref/ship-it"><img src="https://agentmods.dev/badge/skills/smana/cloud-native-ref/ship-it/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/smana/cloud-native-ref/ship-it"><img src="https://agentmods.dev/badge/skills/smana/cloud-native-ref/ship-it.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.00099 | $0.01097 |
| Opus 5.5 | $0.00040 | $0.00439 |
| Sonnet 5.5 | $0.00020 | $0.00219 |
| Haiku 4.5 | $0.00010 | $0.00110 |
Grade A, and why
ship-it 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.
How it starts
The opening of the file, as written. The whole thing — 108 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ship it
One ordered pipeline from "implementation done" to "PR open". The order is the point: each stage feeds the next, and running them out of order wastes the work of the ones before it.
1. commit get the work onto the branch, so nothing can be stranded
2. sync-branch rebase onto origin/main, so every later stage sees the real merge base
3. simplify quality cleanup, while the diff is still yours to reshape
4. prune prose comment + doc concision pass
5. evidence gate run the validators, cite the output
6. review the reviewer sees the final shape, not a draft
7. act on findings fix, then re-run the evidence for whatever moved
8. commit + push + PR
Stop at any stage that fails. A stage that cannot pass is a finding, not something to note and carry forward.
1. Commit what exists
Run the commit skill on whatever is uncommitted. This comes first for a mechanical reason:
sync-branch refuses to rebase a dirty tree, so the pipeline cannot reach stage 2 from the state
it is normally invoked in — implementation finished, nothing committed yet.
If the work is already committed, skip straight to stage 2.
2. Rebase
Run the sync-branch skill. A review against a stale merge base reviews code that will not merge.
Do not let it push here. Stages 3–7 will rewrite the branch again; publishing now would force-push twice and diverge anyone else's checkout for no reason. The push belongs to stage 8.
3. Simplify
Reuse, simplification, efficiency, altitude. Quality only — this is not the bug hunt.
Host mapping: /simplify in Claude Code; otherwise review the diff yourself against those four
axes. Keep it to code you actually changed.
4. Prune prose
Apply the gauntlet in references/prose.md to every comment, doc and
message this branch adds or touches. The bar is asymmetric: deleting a real warning costs more
than leaving a mediocre comment, so keep anything you are unsure about and flag it.
What ships with it
2 files 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.
- 1mo ago First seen · 108 lines · 99 tokens per session scan A eaf87a513996
ship-it is a skill published in the GitHub repository Smana/cloud-native-ref (104 stars, last pushed today), licensed Apache-2.0. It adds 99 tokens to every session and 1,097 once invoked, about $0.0004 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-09-18.
Other skills, from other repositories
review-implement-phase
Implements triaged review actions, commits focused fixes, and posts Done plus resolves threads. Use when the user wants only the implementation phase of the review-framework workflow.
github-pr-workflow
Prepare a GitHub pull request from a feature branch — branch hygiene, commit shape, title/body, verification notes, screenshots for UI work, and replies to review comments.
review-delta
Review only changes since last commit using impact analysis. Token-efficient delta review with automatic blast-radius detection.
git
Git and code hosting platform management — GitHub, GitLab, Codeberg, Forgejo. Zero barrier — install x-cmd and manage repos from the terminal. Use for "git", "github", "gitlab", "repo", "pull request", "code hosting".
github-contributor
A step-by-step guide for contributing code, tests, documentation, or build changes to open-source projects you do not maintain. It explains how to prepare a pull request that follows the project’s rules and is easier for maintainers to review.
atmos-git
Atmos Git and GitOps: git.repositories, clone/pull/status/diff/commit/push/clean, local Git hook shims and hook env vars, pre-commit framework migration, Starlark git.sandbox checks and unstaged fixes, signed commits, managed workdirs, fork-PR trust gate (clone gate and posting gate), and auth via identities or…