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 sailingnaturali/claude-skills --skill oss-branch-protectiongit clone --depth 1 https://github.com/sailingnaturali/claude-skillsWrote 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/sailingnaturali/claude-skills/oss-branch-protection)<a href="https://agentmods.dev/skills/sailingnaturali/claude-skills/oss-branch-protection"><img src="https://agentmods.dev/badge/skills/sailingnaturali/claude-skills/oss-branch-protection/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/sailingnaturali/claude-skills/oss-branch-protection"><img src="https://agentmods.dev/badge/skills/sailingnaturali/claude-skills/oss-branch-protection.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.00092 | $0.00845 |
| Opus 5 | $0.00046 | $0.00423 |
| Sonnet 5 | $0.00018 | $0.00169 |
| Haiku 4.5 | $0.00009 | $0.00085 |
Grade A, and why
oss-branch-protection 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 5d 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 — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.
OSS branch-protection template
One protection policy for every public, non-fork repo in an org, applied idempotently with a single script. The policy binds contributors, not the solo maintainer.
The policy
Applied to each repo's default branch:
| Setting | Value | Why |
|---|---|---|
enforce_admins |
false | The maintainer (admin) stays exempt — keeps a direct-commit-on-main + force-push-after-cleanup workflow. Everything below binds non-admins only. |
| Required status checks | the repo's CI gate, strict (branch up to date) |
No red-CI merges. |
| Required PR reviews | none | A solo maintainer can't self-approve, so requiring reviews would just block them. External contributors have no write access — they must PR anyway, and CI gates the merge. |
| Force-push / delete branch | blocked (non-admins) | Protects history. Admins bypass via enforce_admins: false. |
required_conversation_resolution |
true | PR threads resolve before merge. |
Key idea: enforce_admins: false is what makes a strict policy compatible with a
solo maintainer who commits directly. Contributors get the guardrails; the owner keeps
their flow. If your org has multiple committers and wants review enforcement, set
required_pull_request_reviews and enforce_admins: true instead.
Deriving the CI gate
Required-check names vary by CI, so the applier reads the checks reported on the default branch's latest commit and picks a stable gate:
- Prefer an aggregate gate if present (e.g. a
CI Statussummary job) — stable across matrix changes, unlike per-OS/per-version legs. - Otherwise require the remaining real checks (test matrix, scanners,
build). - Drop non-gating / unstable contexts: anything matrix-templated (
${{ … }}),dependabot,deploy,publish, and site-only jobs (crosspost,report-build-status,update-uv-graph). These either don't report onpull_requestor would wedge PRs waiting on a check that never runs. - No CI on the latest commit → uniform rules only, no required check. Add a
pull_request-triggered workflow first, then re-run to attach a gate.
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.
- 5d ago First seen · 65 lines · 92 tokens per session scan A 5b2b82611530
oss-branch-protection is a skill published in the GitHub repository sailingnaturali/claude-skills (2 stars, last pushed 7d ago), licensed MIT. It adds 92 tokens to every session and 845 once invoked, about $0.0005 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-09-07.
Other skills, from other repositories
prowler-commit
Creates professional git commits following conventional-commits format. Trigger: When creating commits, after completing code changes, when user asks to commit.
gh-auth-isolation
Safely manage multiple GitHub identities (EMU + personal) in agent workflows.
comet-github
A routing guide for Comet-related GitHub work. It directs requests about pull requests, issues, CI failures, ideas, and fixes to the appropriate review or implementation process.
github-skill
Work with GitHub via the gh CLI — clone repositories, create/list/merge pull requests, create/list issues, and run any other gh command (API calls, workflow runs, releases, repo administration). List operations return parsed JSON.
changelog-composer
Generates structured changelogs and release notes from git history and PRs, classifying breaking changes, features, fixes, performance, docs. Triggers on: "generate changelog", "write release notes", "what changed since", "prepare release", "release notes for", "diff since tag".
re0-merge
Review and land an external contribution the way this suite does: gate it against the thesis, land it with the author's credit intact, complete a new skill rather than merging it raw, then approve, credit, and explain before closing. Use when reviewing a pull request, as any collaborator or maintainer, not only the…