Borrowing it
Nothing to install: this file belongs to yorkie-team/yorkie-js-sdk. 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-js-sdk/main/.claude/skills/maintainer-merge/SKILL.mdgit clone --depth 1 https://github.com/yorkie-team/yorkie-js-sdkWrote 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-js-sdk/maintainer-merge)<a href="https://agentmods.dev/skills/yorkie-team/yorkie-js-sdk/maintainer-merge"><img src="https://agentmods.dev/badge/skills/yorkie-team/yorkie-js-sdk/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-js-sdk/maintainer-merge"><img src="https://agentmods.dev/badge/skills/yorkie-team/yorkie-js-sdk/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.00066 | $0.02463 |
| Opus 5.5 | $0.00026 | $0.00985 |
| Sonnet 5.5 | $0.00013 | $0.00493 |
| Haiku 4.5 | $0.00007 | $0.00246 |
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 20d 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 — 178 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-js-sdk/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-29. Re-check if a merge behaves unexpectedly —
gh api repos/yorkie-team/yorkie-js-sdk --jq '{squash:.allow_squash_merge,merge:.allow_merge_commit,rebase:.allow_rebase_merge,msg:.squash_merge_commit_message}'
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 |
squash_merge_commit_message |
COMMIT_MESSAGES |
The default body is every commit message concatenated, agent fix rounds included. Pass --body-file |
required_status_checks.contexts |
[] |
Nothing is required. A red PR will merge. Read the check runs yourself |
required_status_checks.strict |
true | Up-to-date is still required. --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. Bot reviews (coderabbit, the agent panel) do not count |
enforce_admins |
false | --admin is available — see below before using it |
A branch behind main
mergeStateStatus reports BLOCKED for the missing review and hides that
the branch is also behind, so ask directly:
gh api repos/yorkie-team/yorkie-js-sdk/compare/main...<headRef> \
--jq '{behind:.behind_by,ahead:.ahead_by}'
If behind > 0, bring main in with gh pr update-branch <N> (same-repo PRs;
the merge commit disappears in the squash), then wait for CI on the new head
with gh pr checks <N> --watch. Confirm the check runs belong to the new
head — gh api repos/yorkie-team/yorkie-js-sdk/commits/<sha>/check-runs —
before merging. agent-review-docs and agent-deferred-findings finish
neutral normally; build (22.x) and test are the ones that must pass.
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.
- 20d ago Changed · -1 lines ef8c957a1166
- 24d ago Changed · +55 lines 47648eda7ec3
- 28d ago Changed · +13 lines 7ca61161ca04
- 1mo ago First seen · 111 lines · 66 tokens per session scan A 5c246df107b6
maintainer-merge is a skill published in the GitHub repository yorkie-team/yorkie-js-sdk (163 stars, last pushed yesterday), licensed Apache-2.0. It adds 66 tokens to every session and 2,463 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-30.
Other skills, from other repositories
create-pr
Creates a GitHub PR with a Linear-ticket-prefixed title and a decision-led, narrative description for Prisma 8. Use when the user wants to create a pull request, open a PR, or submit changes for review.
git-commit
Generate well-formatted git commit messages following conventional commit standards.
repo-sync
Manage automatic Git syncing on macOS with repo-sync. Use only when the user explicitly invokes /repo-sync.
mcore-split-pr
Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.
engineer-bot-ops
A workflow for carrying an engineering task from scope through implementation and reviewable delivery. It works with a repository's branch, existing changes, rules, checks, and permissions while separating completed, unverified, and next-step work.
contributing
How to contribute to evlog, covering commit and PR conventions, changesets, the Definition of Done, testing rules, and the authored skills that walk through building a new adapter, enricher, framework integration, or map rule. Load this for any question about contributing, opening a PR, or adding something to the…