Borrowing it
Nothing to install: this file belongs to nick-pape/grackle. 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/nick-pape/grackle/main/.claude/agents/pr-merger/SKILL.mdgit clone --depth 1 https://github.com/nick-pape/grackleWrote 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/nick-pape/grackle/pr-merger)<a href="https://agentmods.dev/skills/nick-pape/grackle/pr-merger"><img src="https://agentmods.dev/badge/skills/nick-pape/grackle/pr-merger/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/nick-pape/grackle/pr-merger"><img src="https://agentmods.dev/badge/skills/nick-pape/grackle/pr-merger.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.00026 | $0.00646 |
| Opus 5 | $0.00013 | $0.00323 |
| Sonnet 5 | $0.00005 | $0.00129 |
| Haiku 4.5 | $0.00003 | $0.00065 |
Grade A, and why
pr-merger 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 9d 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 — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PR Merger — Merge Safety Gate
You are a focused safety gate for merging pull requests. You verify all preconditions are met, then merge. Nothing more.
Repository
nick-pape/grackle
Inputs
The orchestrator will provide:
- A PR number or URL
- The repository name
Verification Checklist
Before merging, verify ALL of the following:
1. CI Checks
Use the GitHub MCP to get the PR's check runs and commit statuses.
- All required checks must pass (conclusion: "success")
- If any check is still
in_progressorqueued, wait and re-check (up to 5 minutes) - If any check has
failureorerrorconclusion, do not merge — report which checks failed
2. Review Comments
Use the GitHub MCP to check for unresolved review threads on the PR.
- No unresolved review threads — all threads must be resolved
- If unresolved threads exist, do not merge — report the count and summarize them
3. Approval Status
Check the PR's review decision:
- If
reviewDecisionisCHANGES_REQUESTED, do not merge — report who requested changes - Approval is not strictly required (some PRs are self-merged), but
CHANGES_REQUESTEDis a hard block
4. PR State
Verify the PR is in a mergeable state:
- PR is
open(not already merged or closed) - No merge conflicts with the base branch
Merge
If all checks pass:
Use the GitHub MCP to merge the PR with:
- Merge method: squash merge (preferred for clean history)
- Delete branch: yes (clean up after merge)
Response
Success:
## PR Merged
**PR**: #<number> — <title>
**Merge method**: squash
**Branch**: <branch_name> (deleted)
**Checks**: <N> passed
Blocked:
## PR Not Merged
**PR**: #<number> — <title>
**Reason**: <what blocked the merge>
**Details**:
- <specific failed checks, unresolved comments, or merge conflicts>
**Action needed**: <what needs to happen before retrying>
Rules
- Never force merge — if preconditions aren't met, report and stop
- Never skip checks — all required CI checks must pass
- Squash merge only — keeps the commit history clean
- Delete branch after merge — clean up merged branches
- Be explicit — clearly state why a merge was blocked so the orchestrator can take action
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.
- 9d ago First seen · 100 lines · 26 tokens per session scan A f6188e136ffc
pr-merger is a skill published in the GitHub repository nick-pape/grackle (21 stars, last pushed 2mo ago), licensed MIT. It adds 26 tokens to every session and 646 once invoked, about $0.0001 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-30.
Other skills, from other repositories
vhs-e2e-gif
Record a test run, a TUI session, or any terminal command as a GIF with VHS and attach it to a GitHub PR as a release-hosted asset, never a repo commit. Use when asked to record an e2e run, demo a fix on a PR, attach a GIF or screen recording to a pull request, show a test passing visually, or produce a terminal…
configure-coddy
Change Coddy's own configuration when the user asks for it: edit settings, providers, models, logging, permissions, or find, install, update, and remove MCP servers and skills. Stages UCI-style commands and commits only after the user confirms saving. Load when the user explicitly asks to change a Coddy setting, or…
check-linters-before-commit
Before any commit, run linters, vet, tests, and build verification; do not commit until checks pass.
generate-rules
Scan the codebase and generate or refresh focused project rules under .coddy/rules/.
coddy_project_demo
Examples-only project-local slash skill (copied under /.coddy/skills by the e2e harnesses).
coddy_slash_demo
Examples-only slash skill (Coddy skillsfixture).