Borrowing it
Nothing to install: this file belongs to jarmak-personal/hvir. 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/jarmak-personal/hvir/main/.claude/skills/hvir-merge-pr/SKILL.mdgit clone --depth 1 https://github.com/jarmak-personal/hvirWrote 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/jarmak-personal/hvir/hvir-merge-pr)<a href="https://agentmods.dev/skills/jarmak-personal/hvir/hvir-merge-pr"><img src="https://agentmods.dev/badge/skills/jarmak-personal/hvir/hvir-merge-pr/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/jarmak-personal/hvir/hvir-merge-pr"><img src="https://agentmods.dev/badge/skills/jarmak-personal/hvir/hvir-merge-pr.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.00045 | $0.00953 |
| Opus 5 | $0.00023 | $0.00477 |
| Sonnet 5 | $0.00009 | $0.00191 |
| Haiku 4.5 | $0.00005 | $0.00095 |
Grade A, and why
hvir-merge-pr 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 3d 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 — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Merge an approved pull request
Treat an explicit $hvir-merge-pr invocation as maintainer approval to merge one pull request.
Do not add a second approval boundary or reproduce GitHub's merge policy in repository tooling.
Resolve the pull-request number before acting:
- Use the number supplied by the maintainer when present.
- Otherwise reuse one only when the latest verified lifecycle handoff in the active interaction identifies exactly one final pull request.
- Ask for one pull-request number when there is no such handoff or more than one candidate is possible.
Never search branches, issues, the Project, or the open pull-request list to guess which pull request the maintainer meant. The accepted pull-request number is the complete merge authority input; do not request a separate issue number or candidate SHA.
Read the acceptance rules in AGENTS.md and CONTRIBUTING.md; reuse unchanged context already
read in this interaction. Do not invoke hvir-review-code or invent review or usage evidence. Review
and implementation already ended at the verified handoff.
Request the protected merge
Read only the accepted pull request's base to keep epic-child integration with its existing owner:
gh pr view <pr> --json baseRefName
Require main. This is a delivery-route guard, not a second mergeability, check, review, head, or
relationship classifier. Then use GitHub's ordinary merge path directly:
gh pr merge <pr> --merge --auto
Never use --admin. The repository ruleset, required checks, review requirements, base freshness,
and GitHub mergeability remain authoritative. --auto lets an approved pull request wait for
those requirements instead of turning transient pending or base-refresh state into another
maintainer turn.
Monitor the accepted pull request until GitHub records the merge or reports a durable failure. Report a failed check, conflict, disabled auto-merge, rejected merge, or other GitHub blocker as GitHub returned it. Do not manufacture a new commit, change the PR body or relationships, rerun CI, or bypass protection to make the merge pass.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 3d ago Changed · -10 lines 09c6c618212d
- 12d ago First seen · 108 lines · 45 tokens per session scan A da24ace015c5
hvir-merge-pr is a skill published in the GitHub repository jarmak-personal/hvir (2 stars, last pushed today), licensed MIT. It adds 45 tokens to every session and 953 once invoked, about $0.0002 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-31.
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.
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".
re0-merge
Review and land an external contribution the way this suite does: gate it against the thesis, land it with the author's credit intact, complete a new skill rather than merging it raw, then approve, credit, and explain before closing. Use when reviewing a pull request, as any collaborator or maintainer, not only the…