Borrowing it
Nothing to install: this file belongs to Brad-Edwards/aptl. 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/Brad-Edwards/aptl/main/.claude/skills/ship/SKILL.mdgit clone --depth 1 https://github.com/Brad-Edwards/aptlWrote 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/brad-edwards/aptl/ship)<a href="https://agentmods.dev/skills/brad-edwards/aptl/ship"><img src="https://agentmods.dev/badge/skills/brad-edwards/aptl/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/brad-edwards/aptl/ship"><img src="https://agentmods.dev/badge/skills/brad-edwards/aptl/ship.svg" alt="Reviewed on agentmods" width="80" 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.00033 | $0.00882 |
| Opus 5.5 | $0.00013 | $0.00353 |
| Sonnet 5.5 | $0.00007 | $0.00176 |
| Haiku 4.5 | $0.00003 | $0.00088 |
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 2mo 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 — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ship Current Branch
Assumes code is already committed and pushed. Handles: PR creation, CI monitoring, SonarCloud, code review, security review, fixing all issues, and merging.
IMPORTANT: NEVER include Co-Authored-By, "Generated with Claude Code", or any Claude/AI attribution in commit messages, PR descriptions, or any other artifacts.
Phase 1: Create PR
- Determine the current branch:
git branch --show-current - Check if a PR already exists:
gh pr list --head <branch> --json number,url - If no PR exists, create one:
gh pr create --base dev --title "<concise title>" --body "<description>" - Note the PR number.
Phase 2: CI Monitor
- Find the latest workflow run:
gh run list --branch <branch> --limit 1 --json status,conclusion,databaseId - If the run is in progress, watch it:
gh run watch <id> - If it failed:
- Get failed logs:
gh run view <id> --log-failed - Diagnose and fix the issue.
git add,git commit,git push.- Go back to step 1.
- Get failed logs:
- If it succeeded, proceed.
Phase 3: SonarCloud Check
- Wait 60 seconds for SonarCloud analysis to propagate.
- Use
get_project_quality_gate_statuswith project keyBrad-Edwards_aptlto check the quality gate. - Use
search_sonar_issues_in_projectsto find new issues on the current branch. - If issues found:
- Fix them.
git add,git commit,git push.- Re-run Phase 2.
- If clean, proceed.
Phase 4: Code Review
CRITICAL: You MUST use the Skill tool to invoke the built-in review skill.
- Merge dev into the current branch:
git fetch origin dev && git merge origin/dev - If there are merge conflicts, resolve them, commit, and push.
- Call the Skill tool with
skill="review"to invoke the real built-in code review. - After the review completes, fix ALL issues it identified.
- Do NOT defer ANY issues.
- Do NOT categorize issues as "low priority" to avoid work.
- You are an LLM. You have no time constraints. Fix everything.
- The ONLY reason to stop and escalate to the user is if a fix requires a significant architectural change touching 5+ files outside the current feature scope.
- After fixing, re-read all findings and confirm each one was addressed.
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.
- 2mo ago First seen · 88 lines · 33 tokens per session scan A acecd8311b89
ship is a skill published in the GitHub repository Brad-Edwards/aptl (25 stars, last pushed 24d ago), licensed MIT. It adds 33 tokens to every session and 882 once invoked, about $0.0001 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-08-30.
Other skills, from other repositories
otto-drive-pr
PR mergeability, CI, and live preview.
no-mistakes
Validate committed feature-branch changes through the no-mistakes pipeline: intent, rebase, review, test, docs, lint, push, PR, and CI. Use when the user asks to run no-mistakes, ship safely, validate before pushing, or gate a change before it reaches upstream.
github
GitHub-centric templates — pull requests, issue triage, repo automation.
git-monorepo-release
A release workflow for a monorepo—a single repository containing several packages that can each have their own version.
git-release-tag
A release helper for Git repositories that chooses a semantic version tag, such as patch, minor, or major, from the commits since the previous tag. It also builds release notes and can create a GitHub Release after confirmation.
fable-release
Audit and certify repository merge and release readiness against required quality gates, clean git working trees, and verified distribution artifacts. Use when preparing a release tag, validating release checklist criteria, publishing npm/PyPI packages, or certifying a branch for merge — even if the user does not…