Borrowing it
Nothing to install: this file belongs to tbhb/vale-ai-tells. 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/tbhb/vale-ai-tells/main/.claude/skills/codex-merge-pr/SKILL.mdgit clone --depth 1 https://github.com/tbhb/vale-ai-tellsWrote 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/tbhb/vale-ai-tells/codex-merge-pr)<a href="https://agentmods.dev/skills/tbhb/vale-ai-tells/codex-merge-pr"><img src="https://agentmods.dev/badge/skills/tbhb/vale-ai-tells/codex-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/tbhb/vale-ai-tells/codex-merge-pr"><img src="https://agentmods.dev/badge/skills/tbhb/vale-ai-tells/codex-merge-pr.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00121 | $0.02601 |
| Opus 5 | $0.00060 | $0.01300 |
| Sonnet 5 | $0.00024 | $0.00520 |
| Haiku 4.5 | $0.00012 | $0.00260 |
Grade A, and why
codex-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 11d 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 — 181 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Merge a pull request
Work the steps in order. Codex doesn't provide skill-scoped command hooks, so the scripts enforce the terminal invariants while these instructions keep every mutating command on the sanctioned path. Never run gh pr merge directly.
Left alone, GitHub writes the squash message by concatenating every commit on the branch. That text has never passed a commit-msg hook, and it arrives on the default branch where the rest of the toolchain assumes those hooks ran. Nothing lints it afterwards. This workflow writes the message itself and puts it through what a commit answers to.
Preflight
Run bash .agents/skills/codex-merge-pr/scripts/preflight.sh [number], passing the pull request number when the request names one.
Step 0: open the task list
Create these with update_plan, keeping exactly one item in_progress at a time.
- Confirm the pull request is mergeable
- Settle the published description
- Write the squash message in SQUASH_AGENTMSG
- Review the message with codex-review-squash-message
- Run the commit-msg gates
- Confirm the message with the operator
- Merge and clean up
Stop before any of it where preflight reports a missing precondition, a draft pull request, or a failing check. Say what's wrong and hand back.
Step 1: confirm the pull request is mergeable
Preflight printed the state, the check rollup, and the review decision. Merging needs an open pull request that nobody marked as a draft, with every check green.
A failing check goes to codex-fix-pr, and a running one goes to codex-watch-pr. Neither belongs here, and the merge script refuses both anyway.
A mergeStateStatus of BEHIND or DIRTY is the third case. The branch needs the base underneath it before anything merges, so run the codex-rebase skill and push the result. Don't reach for GitHub's own update button: it merges the base into the branch, which leaves a merge commit this workflow never wrote a message for.
Where the repository requires a review decision, respect it. CHANGES_REQUESTED means the merge waits, whatever the checks say.
What ships with it
6 files 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.
- 11d ago First seen · 181 lines · 121 tokens per session scan A 008b248509f7
codex-merge-pr is a skill published in the GitHub repository tbhb/vale-ai-tells (92 stars, last pushed yesterday), licensed MIT. It adds 121 tokens to every session and 2,601 once invoked, about $0.0006 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
anti-slop
Remove AI slop from any voice-bearing prose — original posts, threads, articles, long-form, emails, docs, READMEs, marketing copy, bios, scripts. Use when drafting text meant to sound like a specific person or brand, when rewriting text that reads generic, corporate, or AI-generated, or when asked to humanize…
kill-slop
Audit a file or draft for AI slop and off-voice lines against the author's bound voice, report findings with in-voice swaps, then apply approved fixes. Use when the user says "kill slop", "/kill-slop [file]", "find the slop in this", "audit this for slop", or wants a deck, article, page, or draft cleaned to sound like…
contextual-commit
Write contextual commits that capture intent, decisions, and constraints alongside code changes. Use when committing code, finishing a task, or when the user asks to commit. Extends Conventional Commits with structured action lines in the commit body that preserve WHY code was written, not just WHAT changed.
gh-issues
Fetch GitHub issues, spawn sub-agents to implement fixes and open PRs, then monitor and address PR review comments. Usage: /gh-issues [owner/repo] [--label bug] [--limit 5] [--milestone v1.0] [--assignee @me] [--fork user/repo] [--watch] [--interval 5] [--reviews-only] [--cron] [--dry-run] [--model glm-5]…
git-commit
Generate well-formatted git commit messages following conventional commit standards.
git-commit
Stage, write, and structure git commits and pull requests cleanly. Read this before committing — for conventional-commit message format, when to split commits, and how to open a PR with the gh CLI.