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 matteocervelli/llms --skill pr-mergegit clone --depth 1 https://github.com/matteocervelli/llmsWrote 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/matteocervelli/llms/pr-merge)<a href="https://agentmods.dev/skills/matteocervelli/llms/pr-merge"><img src="https://agentmods.dev/badge/skills/matteocervelli/llms/pr-merge.svg" alt="Measured on agentmods" 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.00062 | $0.01607 |
| Opus 5 | $0.00031 | $0.00804 |
| Sonnet 5 | $0.00012 | $0.00321 |
| Haiku 4.5 | $0.00006 | $0.00161 |
Grade A, and why
pr-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 6d 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 — 227 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PR Merge
Overview
This skill enables safe and comprehensive pull request merging workflows using GitHub MCP tools. It automates the complete pre-merge validation process, checks CI/CD status, verifies reviews, and executes merges with the appropriate merge strategy.
When to Use This Skill
Use this skill when the user requests:
- "Merge PR #123"
- "Can we merge this pull request?"
- "Check if PR is ready to merge"
- "Complete the PR workflow"
- "Merge this feature branch"
- "Is PR #456 ready to be merged?"
Pre-Merge Validation Workflow
Before merging any PR, execute the complete validation workflow to ensure safety and quality.
Step 1: Fetch PR Details
Use mcp__github-mcp__get_pull_request to retrieve:
- PR title and description
- Base and head branches
- Draft status
- Current state (open/closed)
Required parameters:
owner: Repository ownerrepo: Repository namepullNumber: PR number
Step 2: Check CI/CD Status
Use mcp__github-mcp__get_pull_request_status to verify:
- All required checks are passing
- No failed CI/CD workflows
- Branch protection rules are satisfied
Block merge if:
- Any required checks are failing
- Checks are still pending (inform user to wait)
- Branch protection rules are not met
Step 3: Verify Reviews
Use mcp__github-mcp__get_pull_request_reviews to confirm:
- Sufficient approved reviews exist
- No requested changes are outstanding
- Review requirements are met per branch protection
Block merge if:
- Required reviews are missing
- Any reviewer has requested changes
- Review dismissals need to be addressed
Step 4: Check for Conflicts
Use mcp__github-mcp__get_pull_request_diff to identify:
- Merge conflicts with base branch
- File-level conflicts that need resolution
Block merge if:
- Merge conflicts are present (instruct user to resolve)
- Base branch needs to be updated first
Step 5: Review Changes (Optional)
For additional safety, use mcp__github-mcp__get_pull_request_files to:
- Review changed files
- Identify potential issues
- Confirm changes align with PR description
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.
- 6d ago First seen · 227 lines · 62 tokens per session scan A 5ee32f865c35
pr-merge is a skill published in the GitHub repository matteocervelli/llms (25 stars, last pushed 3mo ago), licensed MIT. It adds 62 tokens to every session and 1,607 once invoked, about $0.0003 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-01.
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.
codex-autoresearch
Run autonomous, measurable experiments in a Git repository: change one hypothesis, verify a numeric metric, keep improvements, and revert failures. Use when the user wants Codex to keep iterating toward a numeric target in the foreground or as a detached background run. Do not use for ordinary one-shot coding…
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".