Borrowing it
Nothing to install: this file belongs to auerbachb/claude-code-config. 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/auerbachb/claude-code-config/main/.claude/skills/admin-merge/SKILL.mdgit clone --depth 1 https://github.com/auerbachb/claude-code-configWrote 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/auerbachb/claude-code-config/admin-merge)<a href="https://agentmods.dev/skills/auerbachb/claude-code-config/admin-merge"><img src="https://agentmods.dev/badge/skills/auerbachb/claude-code-config/admin-merge/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/auerbachb/claude-code-config/admin-merge"><img src="https://agentmods.dev/badge/skills/auerbachb/claude-code-config/admin-merge.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 77 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
- medium Excessive Agency · line 117 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00094 | $0.03807 |
| Opus 5.5 | $0.00038 | $0.01523 |
| Sonnet 5.5 | $0.00019 | $0.00761 |
| Haiku 4.5 | $0.00009 | $0.00381 |
Grade A, and why
admin-merge 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 2mo 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 — 159 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Merge a PR whose only remaining blocker is branch protection on a solo-owner repo — either by auto-running the no-protection-change shape, or by printing the protection-toggle command for the user.
Portable helper resolution
Before any step, resolve the required helper. Stop visibly if it is unavailable.
resolve_script() {
local name="$1" candidate
for candidate in \
"$HOME/.claude/skills-worktree/.claude/scripts/$name" \
"$HOME/.claude/scripts/$name" \
".claude/scripts/$name"; do
if [[ -x "$candidate" ]]; then echo "$candidate"; return 0; fi
done
return 1
}
ADMIN_MERGE_SH=$(resolve_script admin-merge.sh || true)
[[ -n "$ADMIN_MERGE_SH" ]] || { echo "ERROR: admin-merge.sh not found (checked all three paths) — admin merge unavailable" >&2; exit 1; }
The safety boundary (non-negotiable) — a split, not a blanket
Claude's safety rules permanently prohibit Claude from modifying branch protection — non-negotiable, applies to every user and repo regardless of authorization or workflow history. That prohibition is about protection modification, not about the --admin flag, and the two bypass shapes fall on opposite sides of it (issues #720, #754):
| Shape | Condition | Command | Authority |
|---|---|---|---|
| plain | enforce_admins: false + required_status_checks.strict: true + verified clean-BEHIND |
gh pr merge --squash --admin — nothing else |
Claude auto-runs it via --auto-plain |
| toggle | enforce_admins: true |
DELETE …/enforce_admins → merge → POST …/enforce_admins |
Print-only. The user runs it. |
- Claude MAY execute the plain shape via
"$ADMIN_MERGE_SH" <PR> --auto-plain. It modifies no setting and steps over a staleness requirement, not a review; every safety condition is re-verified programmatically immediately before the merge. No user turn is required. - Claude NEVER executes
gh api -X DELETE .../protection/enforce_admins,gh api -X POST .../protection/..., or any other protection-modification command — not directly, not via a subprocess, not via--execute. For the toggle shape Claude only ever prints (or clipboards) the command. - The skill invokes
admin-merge.shwith--auto-plain,--print, or--launch-terminal. It must never invoke--execute(that mode can run the toggle dance and is reserved for the user in their own terminal). --auto-plainis structurally incapable of the toggle shape: its branch contains no protection-modifying call, and any non-plain shape is a hard refusal (exit 8) that falls back to printing. Mechanism:.claude/reference/admin-merge-auto-plain.md.
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.
- 2mo ago First seen · 159 lines · 94 tokens per session scan A 887bbcff8d8b
admin-merge is a skill published in the GitHub repository auerbachb/claude-code-config (5 stars, last pushed 2d ago), licensed MIT. It adds 94 tokens to every session and 3,807 once invoked, about $0.0004 per session on Opus 5.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
robin
Use whenever an agent creates, updates, reviews, or completes a GitHub pull request. Detect whether Robin is installed in the repository; when it is, automatically drive the PR through a bounded review, verified-fix, reply, thread-resolution, re-review, authorized-merge, and cleanup loop without requiring the user to…
revert
Git-aware revert that understands Draft tracks, phases, and tasks. Safely undo work at task, phase, or track level. Use when the user asks to 'revert this track', 'undo a phase', 'revert task X', or says 'roll back the last task', 'undo this work'.
upload
Pre-upload gate for track handoff. Verifies review status, HLD approvals, deploy checklist, and validator chain before git upload or PR submission.
bump-version
Bump the Logic-Lens version across all six metadata locations at once (package.json, the four plugin manifests, and the README badge), then validate. Use when cutting a release or when npm run validate reports a version mismatch.
kodus-business-rules-validation
Use when the user wants Kodus to validate local diff changes against task requirements, acceptance criteria, or business rules via kodus pr business-validation, especially for implementation-vs-task or merge readiness checks.
Cross-File Leakage リファクタ後の caller 側残骸検出
A code review check for structural changes such as renamed functions, changed arguments, moved files, or split modules. It searches the rest of the project for callers that still use the old structure.