Borrowing it
Nothing to install: this file belongs to fokkerone/superspecs. 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/fokkerone/superspecs/main/.skills/ship/SKILL.mdgit clone --depth 1 https://github.com/fokkerone/superspecsWrote 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/fokkerone/superspecs/ship)<a href="https://agentmods.dev/skills/fokkerone/superspecs/ship"><img src="https://agentmods.dev/badge/skills/fokkerone/superspecs/ship.svg" alt="Measured on agentmods" 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.00053 | $0.00997 |
| Opus 5 | $0.00026 | $0.00498 |
| Sonnet 5 | $0.00011 | $0.00199 |
| Haiku 4.5 | $0.00005 | $0.00100 |
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 7d 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 — 163 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: ship
You are shipping the feature. Final step.
Preconditions — verify before proceeding:
- Tests passing + wiki imported (Phase 3 complete)
- No open Critical review findings
- Branch is on
superspec/<slug>with all commits
If any precondition fails, stop and name the missing step.
Steps
1. Final diff review
git log main..superspec/<slug> --oneline
git diff main..superspec/<slug> --stat
Show a summary: how many files changed, how many commits. No surprises.
2. Write the PR description
## <Feature Name>
### What
<1–2 paragraphs: what was built, from the user/system perspective>
### Why
<The problem this solves, from DISCUSS.md>
### How it works
<Brief technical summary — key decisions, architecture shape>
### Tests
- Suite: X tests, all passing
- New tests: Y (covering N spec scenarios)
### Spec
`superspec/specs/<slug>/spec.md`
### Wiki
<links to new wiki pages>
### Checklist
- [x] Tests passing
- [x] Spec scenarios covered
- [x] Code review passed
- [x] Wiki updated
- [x] No regressions
3. Create the PR
Instruct the user (or if gh CLI is available):
gh pr create \
--base main \
--head superspec/<slug> \
--title "<Feature Name>" \
--body-file /tmp/pr-body.md
Or: output the PR body and say "Create the PR with this description."
4. Write changelog entry
If the project has a CHANGELOG.md:
## [Unreleased]
### Added
- <Feature description> (closes #<issue if applicable>)
5. Archive the spec and phase directories
Move both the spec folder and the phase execution directory into superspec/archive/<slug>/:
mkdir -p superspec/archive/<slug>
mv superspec/specs/<slug> superspec/archive/<slug>/spec
mv superspec/phases/<slug>-execute superspec/archive/<slug>/execute
The archive layout per slug:
superspec/archive/<slug>/
spec/ ← was superspec/specs/<slug>/
execute/ ← was superspec/phases/<slug>-execute/
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.
- 7d ago First seen · 163 lines · 53 tokens per session scan A 500c224acfd0
ship is a skill published in the GitHub repository fokkerone/superspecs (4 stars, last pushed 2mo ago), licensed MIT. It adds 53 tokens to every session and 997 once invoked, about $0.0003 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
release-announcement
Write a release announcement — changelog, blog post, in-app note, or social post — that leads with user impact, names the audience, and includes upgrade/migration steps without filler.
agent-release-swarm
Agent skill for release-swarm - invoke with $agent-release-swarm.
multi-agent-release-manager
Cleans up the workspace, formats code, runs presubmit checks, and uploads CLs to Gerrit.
release-notes
Generate user-facing release notes from tickets, PRDs, or changelogs. Creates clear, engaging summaries organized by category (new features, improvements, fixes). Use when writing release notes, creating changelogs, announcing product updates, or summarizing what shipped.
pack-submit
Package one of this agent's own skills as a standalone community pack and submit it to the aeon registry as a PR.
updater_guide
Guidance for checking for and installing Row-Bot updates.