Borrowing it
Nothing to install: this file belongs to labsai/EDDI. 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/labsai/EDDI/main/.claude/skills/ship-pr/SKILL.mdgit clone --depth 1 https://github.com/labsai/EDDIWrote 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/labsai/eddi/ship-pr)<a href="https://agentmods.dev/skills/labsai/eddi/ship-pr"><img src="https://agentmods.dev/badge/skills/labsai/eddi/ship-pr/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/labsai/eddi/ship-pr"><img src="https://agentmods.dev/badge/skills/labsai/eddi/ship-pr.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.00100 | $0.07045 |
| Opus 5.5 | $0.00040 | $0.02818 |
| Sonnet 5.5 | $0.00020 | $0.01409 |
| Haiku 4.5 | $0.00010 | $0.00705 |
Grade C, and why
ship-pr scanned grade C with 1 finding 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 2d 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
> rm -rf target/surefire-reports How it starts
The opening of the file, as written. The whole thing — 469 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Shipping a branch through review
gh is authenticated for labsai/EDDI. In the desktop app, prefer the ccd_pr tools
(bind_pr, get_status, set_monitor) over polling gh pr checks — they push CI state
to you instead of burning turns on a 20-minute pipeline.
Two things go wrong most often and both are below: a green CodeRabbit row can mean
nothing was reviewed, and most checks in the list do not gate the merge, which makes
them easier, not harder, to ignore.
1. Before the push
Branch name. git branch --show-current, and fix it before anything else.
A
claude/*branch name must never exist anywhere — not on a remote, not locally, not on any repo. The harness names worktree branchesclaude/<slug>; rename it the moment you notice it, before the first commit, not before the first push:git branch -m feat/short-description(orfix/,chore/,refactor/,docs/to match the change). Renaming is free and safe while the branch is unpushed; it is not recoverable once the name is public.
Base. ci.yml's only pull_request trigger is branches: [main] (it also runs on
pushes to main and on release tags). A PR into any other branch runs no CI at all,
silently. If the work is stacked, retarget once the parent merges, or accept that the local
build is the only gate and say so. Rebase onto origin/main only if the branch was never
pushed — otherwise merge origin/main in, since a rebase would need a banned force-push.
Changelog — a fragment, never the live file. AGENTS.md §2 rule 8: write a new
file docs/changelog.d/YYYY-MM-DD-<slug>.md (today's date, slug unique to your branch) and
commit it on the same branch as the work.
Do not edit
docs/changelog.mdby hand. CI'sChangelog Disciplinejob diffs that file against the base and fails the PR if the diff adds a line matching^\+## .*\(YYYY-MM-DD\)or a dated register row^\+\| YYYY-MM-DD \|. Editing the header or fixing a typo in a past entry is still fine — adding an entry in place is the one thing it rejects, because every open PR inserting at the same point in the same file is a conflict git cannot merge.
What ships with it
1 file 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.
- 2d ago Changed · +2 lines feef0d3718bf
- 1mo ago Changed · -1 lines 33a002e9c96d
- 1mo ago First seen · 468 lines · 100 tokens per session scan C 619d6ccbc103
ship-pr is a skill published in the GitHub repository labsai/EDDI (387 stars, last pushed today), licensed Apache-2.0. It adds 100 tokens to every session and 7,045 once invoked, about $0.0004 per session on Opus 5.5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-25.
Other skills, from other repositories
pr-review-comments
Posts review findings from a JSON file as inline comments on a GitHub Pull Request, attaching each comment to its file and line. Use when you have a list/JSON of review findings (each with a file path, line number, and a message such as summary/failurescenario) and want them published on a PR as inline review…
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.
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.
hero-diff-highlight
A dark code editor reveals a red deletion then a green addition with a soft pulse. Function: PR / code-change explainer.