Borrowing it
Nothing to install: this file belongs to yorkie-team/yorkie. 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/yorkie-team/yorkie/main/.claude/skills/maintainer-merge/SKILL.mdgit clone --depth 1 https://github.com/yorkie-team/yorkieWrote 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/yorkie-team/yorkie/maintainer-merge)<a href="https://agentmods.dev/skills/yorkie-team/yorkie/maintainer-merge"><img src="https://agentmods.dev/badge/skills/yorkie-team/yorkie/maintainer-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/yorkie-team/yorkie/maintainer-merge"><img src="https://agentmods.dev/badge/skills/yorkie-team/yorkie/maintainer-merge.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.00075 | $0.02092 |
| Opus 5.5 | $0.00030 | $0.00837 |
| Sonnet 5.5 | $0.00015 | $0.00418 |
| Haiku 4.5 | $0.00007 | $0.00209 |
Grade A, and why
maintainer-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 27d 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 — 138 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Maintainer Merge
Overview
Most of this procedure is derivable: gh pr view, gh pr checks,
gh api repos/yorkie-team/yorkie/branches/main/protection, and
.githooks/commit-msg tell you the state, the gates and the message rules.
Derive those. This file carries only what the repository cannot tell you,
plus the settings worth knowing before you spend calls rediscovering them.
Core principle: check the settings, and report what you actually did.
Settings that decide the path
Verified 2026-09-23. Re-check if a merge behaves unexpectedly —
gh api repos/yorkie-team/yorkie --jq '{squash:.allow_squash_merge,merge:.allow_merge_commit,auto:.allow_auto_merge}'
and the branches/main/protection endpoint.
| Setting | Value | Consequence |
|---|---|---|
allow_squash_merge |
true, and it is the only one | -m/-r are rejected by the API |
allow_auto_merge |
false | --auto is unavailable; wait, or gh pr checks --watch |
squash_merge_commit_message |
COMMIT_MESSAGES |
The default body is every commit message concatenated. Pass --body-file |
required_status_checks.contexts |
[] |
Nothing is required. A red PR will merge. Read gh pr checks yourself |
required_status_checks.strict |
true | Up-to-date is still required. A behind branch reports BEHIND and the merge refuses — rebase it. --admin would bypass this and merge a combination nothing tested |
required_approving_review_count |
1 | MERGEABLE + BLOCKED means the review is missing, not a check |
dismiss_stale_reviews |
false | New commits do not dismiss an existing approval, so a rebase you push leaves the PR approved for a head nobody read |
require_last_push_approval |
false | The latest push needs no approval from someone other than its pusher — it does not govern dismissal, which is the row above |
enforce_admins |
false | --admin is available — see below before using it |
delete_branch_on_merge |
true | Redundant for same-repo PRs. Does nothing for a fork — GitHub only auto-deletes in its own repo, so the fork branch survives; tell the contributor |
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.
- 27d ago Changed · +15 lines 765ccbbb2d2d
- 1mo ago First seen · 123 lines · 75 tokens per session scan A 0ec93131de37
maintainer-merge is a skill published in the GitHub repository yorkie-team/yorkie (930 stars, last pushed yesterday), licensed Apache-2.0. It adds 75 tokens to every session and 2,092 once invoked, about $0.0003 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-09-24.
Other skills, from other repositories
conventional-commit
Rules for writing Conventional Commits messages in this project. MUST be invoked every time a commit is created.
conventional-commit-message
Generate high-quality Conventional Commit messages for repositories using conventional-changelog-conventionalcommits.
implement
Drive a single workshop ticket through the inner SWE↔Tester loop. Resolves the ticket from implementyourself/tasks/, creates an implementing/from-scratch branch (a fixed default — not derived from the ticket; subsequent tickets stack on top), launches the software-engineer agent to implement it, then routes by…
update-changelog
Update the CHANGELOG.md files of C# projects. Parameters: csroot C# SDK repository root.
repository-assisted-apply
Safely review, apply, verify, activate, and record one user-selected object in an ABAP FS Copilot-assisted repository-comparison workflow. Use only after the repository workflow has a prepared assisted-apply plan and the user has enabled Copilot-assisted apply.
ui-visual-regression
Automates visual regression testing for DB Console UI changes. Compares screenshots and network requests between the current branch and its merge base using roachprod, playwright-cli, and ImageMagick. Use when the user wants to verify UI changes haven't introduced visual or behavioral regressions.