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 mhylle/claude-skills-collection --skill ship-issuegit clone --depth 1 https://github.com/mhylle/claude-skills-collectionWrote 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/mhylle/claude-skills-collection/ship-issue)<a href="https://agentmods.dev/skills/mhylle/claude-skills-collection/ship-issue"><img src="https://agentmods.dev/badge/skills/mhylle/claude-skills-collection/ship-issue/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/mhylle/claude-skills-collection/ship-issue"><img src="https://agentmods.dev/badge/skills/mhylle/claude-skills-collection/ship-issue.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.00088 | $0.06355 |
| Opus 5 | $0.00044 | $0.03178 |
| Sonnet 5 | $0.00018 | $0.01271 |
| Haiku 4.5 | $0.00009 | $0.00636 |
Grade A, and why
ship-issue 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 11d 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 — 318 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/ship-issue — Issue-to-Merge Pipeline Orchestrator
You are the ship-issue orchestrator, running in the Fable 5 main session. Your goal: take one GitHub issue from reference to merged PR through the nine pipeline stages — preflight, plan, implement, review, ci, cloud_review, deploy, e2e, logs — pausing only at the two human gates. You are the single writer of run state (ADR-0009): every state mutation goes through python3 skills/ship-issue/scripts/run_state.py; everything else (dashboard, readers) only reads state.json and events.jsonl.
Binding contracts — conform to these, do not reinvent them:
- references/stage-contracts.md — the nine stage contracts and both gates; gates are not stages
- references/run-state-schema.md — state.json, events.jsonl, pause semantics, time summary
- references/config-schema.md — the target-repo config preflight validates
- references/model-tiering.md — pinned model tiers; fresh task on the same pinned tier
- references/prompt-rules.md — per-tier prompt style for every task you dispatch
Arguments
Accept an issue number (142) or a full GitHub issue URL (https://github.com/<owner>/<repo>/issues/142). Ingest the issue with:
gh issue view <n> --json number,title,url,body
The issue's number, title, url, and body are the run's founding inputs.
Resume on re-invocation — check FIRST
Before starting anything new, scan .ship-issue/runs/*/state.json in the target repo for an existing run of this issue whose events.jsonl contains no run_completed and no run_aborted event. If one exists, this invocation is a resume, not a new run:
python3 skills/ship-issue/scripts/run_state.py resume-check --run-dir <run-dir>
Continue at the printed resume point:
RESUME_AT: gate:gate_1— re-present Gate 1 with the persisted plan and wait for the decision. The elapsed wait is gate wait, already covered by the open gate-wait window.RESUME_AT: stage:<s>— re-enter stage<s>. If a work window was open at the crash,resume-checkhas already recorded the dead window as acrash_gap_recordedevent and opened a fresh work window.
What ships with it
11 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.
- pipeline.html 21 KB
- references/config-schema.md 7.6 KB
- references/model-tiering.md 4.9 KB
- references/prompt-rules.md 6.4 KB
- references/run-state-schema.md 18 KB
- references/stage-contracts.md 16 KB
- scripts/cloud_review.py 6.2 KB runs code
- scripts/dashboard.py 14 KB runs code
- scripts/merge_brief.py 6.3 KB runs code
- scripts/preflight.py 8.3 KB runs code
- scripts/run_state.py 32 KB runs code
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.
- 11d ago First seen · 318 lines · 88 tokens per session scan A d0f02137c623
ship-issue is a skill published in the GitHub repository mhylle/claude-skills-collection (18 stars, last pushed 8d ago), licensed MIT. It adds 88 tokens to every session and 6,355 once invoked, about $0.0004 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
mcore-split-pr
Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.
shiplog
Recap of everything shipped since the last run - cross-repo PRs, security fixes, star deltas, and X traction, synthesized into a digest article and a ready-to-post shiplog in your voice.
llxprt-issue-workflow
Use this skill when asked to address, fix, or work on a GitHub issue in the llxprt-code repository. Covers the complete issue lifecycle - branch setup, gh CLI usage, test-first planning, subagent delegation and review loops, the full verification cycle (including the stepfun-37 smoke test), open code review (ocr), PR…
cyrus-setup-repository
Add one or more Git repositories to Cyrus configuration so it can process issues from those repos.
github-sync
Bidirectional synchronization of epics and tasks with GitHub issues, labels, and relationships.
github-notification-triage
Triage GitHub notifications and issue/PR queues.