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 goiltpatpat/patpat --skill patpat-shipgit clone --depth 1 https://github.com/goiltpatpat/patpatWrote 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/goiltpatpat/patpat/patpat-ship)<a href="https://agentmods.dev/skills/goiltpatpat/patpat/patpat-ship"><img src="https://agentmods.dev/badge/skills/goiltpatpat/patpat/patpat-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/goiltpatpat/patpat/patpat-ship"><img src="https://agentmods.dev/badge/skills/goiltpatpat/patpat/patpat-ship.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.00057 | $0.00648 |
| Opus 5 | $0.00028 | $0.00324 |
| Sonnet 5 | $0.00011 | $0.00130 |
| Haiku 4.5 | $0.00006 | $0.00065 |
Grade A, and why
patpat-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 — 28 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Patpat Ship
When invoked directly, read the operating protocol and execution graph in full. Do not load the router.
Read preserve safety, proof over proxy, and the operating protocol.
After verify and review pass, require delivery intent: explicit commit, PR, or ship language; overnight or continuation; or explicit land or merge. Explicit /patpat activation alone is not delivery authority. Also require that no higher-priority repository rule forbids delivery. Then apply default delivery: commit the in-scope diff, use a non-force push, and open or update one ready pull request unless the user opted out or the path was read-only.
Apply authorized delivery to merge, publish, or deploy. Only explicit land or merge language authorizes merge. Overnight, going to bed, or don't stop drives a verified pull request to merge-ready and stops. Do not land a real CI failure. Retry a flake once.
For watch CI, babysit, get it green, or unattended merge-ready work, use PR babysit. On GitHub.com, capture one bounded read-only observation with scripts/github_observe.py, then evaluate it with scripts/pr_watch.py. Keep expected repository, pull request, head, base, required checks, deadline, and attempt budget explicit. Source required checks from the repository's verified branch policy or CI contract. An empty required-check set remains blocked, including when the legacy --allow-no-required-checks flag is present, because the current observation does not bind provider policy evidence. Rebind on stale, reobserve on pending, stop and diagnose on blocked, and stop merge-ready on ready. Neither script grants delivery authority or mutates the provider.
Inspect version-control state, unrelated dirty files, and secrets before any git write. Workers never ship. Re-check the remote revision after the action.
Pause for production deploy, package publish, force-push, secret rotation, and risky auth, billing, or permission changes. Explain blast radius, rollback, and verification before continuing.
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.
- 7d ago Changed · -2 tokens per session ea745b80b6eb
- 10d ago First seen · 28 lines · 59 tokens per session scan A a6df3699a34d
patpat-ship is a skill published in the GitHub repository goiltpatpat/patpat (1 stars, last pushed today), licensed MIT. It adds 57 tokens to every session and 648 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
git-authoring
Authors and executes git work end to end — Conventional Commits messages, pull-request content, release notes, and pull-request review, plus the repository operations an engineer runs daily: branching, rebasing, squashing, cherry-picking, reverting, merge-conflict resolution, stashes, tags, remotes, and recovery…
wiki-changelog
Analyzes git commit history and generates structured changelogs categorized by change type. Use when the user asks about recent changes, wants a changelog, or needs to understand what changed in th...
git-workflow-and-versioning
Structures git workflow practices. Use when making any code change. Use when committing, branching, resolving conflicts, splitting uncommitted work in a messy working tree into clean atomic commits, opening or reviewing a pull request (PR), pushing to a remote, or when you need to organize work across multiple…
work-unit-commits
Plan commits as reviewable work units. Trigger: implementation, commit splitting, chained PRs, or keeping tests and docs with code.
github-release-briefing-skill
Create a source-linked briefing for the latest published GitHub release of a public repository. Use for engineering teams tracking a dependency release; do not use it to publish releases or change repositories.
ijfw-ship
Use when the user says 'ship it', 'ship this', 'release', 'publish', 'launch', 'deploy', 'go live', 'wrap this up', 'time to ship', or invokes '/ijfw-ship'. Domain-aware release — software (test → tag → push → publish), book (final edit → format → KDP / agent / Substack), campaign (review → schedule → launch →…