PoseCap: Skill for Codex

.agents/skills/ad-merge/SKILL.md

ad-merge is a skill for Codex from CorridorTech/PoseCap. It costs 134 tokens per session (1,306 once invoked), scanned A, original, Apache-2.0.

A pull-request review and merge assistant for GitHub, the service where teams host code and review proposed changes. It checks a pull request and can merge it using the repository’s chosen merge style.

In plain words
What is it for?
Use it to inspect CI results, unresolved review comments, linked work, and merge status, then merge an eligible pull request through GitHub’s command-line tool.
Why use it?
It gathers the checks and review information needed to decide whether a pull request is ready. It treats passing CI—the automated build and test checks—as the required condition for merging.

Skill for Codex

Written for Codex: agents/openai.yaml present. Also seen: mentions Claude Code; installed under .agents/ (shared by several agents); mentions Codex.

This is CorridorTech/PoseCap's own configuration. It tells Codex how to work on PoseCap itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything PoseCap configures →

Reuse

Borrowing it

Nothing to install: this file belongs to CorridorTech/PoseCap. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/CorridorTech/PoseCap/main/.agents/skills/ad-merge/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/CorridorTech/PoseCap

Made for: Codex.

Wrote 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.

agentmods badge for ad-merge

README.md
[![agentmods](https://agentmods.dev/badge/skills/corridortech/posecap/ad-merge/github.svg)](https://agentmods.dev/skills/corridortech/posecap/ad-merge)
Your own site
<a href="https://agentmods.dev/skills/corridortech/posecap/ad-merge"><img src="https://agentmods.dev/badge/skills/corridortech/posecap/ad-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.

agentmods 80×15 button for ad-merge

Your own site · 80×15
<a href="https://agentmods.dev/skills/corridortech/posecap/ad-merge"><img src="https://agentmods.dev/badge/skills/corridortech/posecap/ad-merge.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 134 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,306 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00134 $0.01306
Opus 5.5 $0.00054 $0.00522
Sonnet 5.5 $0.00027 $0.00261
Haiku 4.5 $0.00013 $0.00131

Measured 2mo ago against content hash d836a1f4c53b, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

ad-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 2mo 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.

.agents/skills/ad-merge/SKILL.md · 103 lines

How it starts

The opening of the file, as written. The whole thing — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.

<background_information> Implements ADR-0025. Evaluates a PR's mergeability and performs the merge via gh pr merge. CI green is the only hard gate; everything else surfaces as a warning the senior engineer decides on.

Codex auto-trigger on description keywords is less mature than Claude Code's. If auto-invocation does not fire when the user mentions merging a PR or evaluating mergeability, invoke this skill manually. </background_information>

Route elsewhere when:

  • No PR exists yet → ad-pr first.
  • Commits are not on the branch yet → ad-commit first.

Phase 1 — preflight. Check gh is installed and authenticated:

gh --version
gh auth status

If absent or not authed, surface the install / gh auth login hint and stop (same soft-fail rule as ad-pr).

Resolve the target PR:

  • If the user passed a PR number / URL, use it.
  • Else gh pr view --json number,headRefName,baseRefName against the current branch. If that fails, surface: "No PR found for branch <name>. Open one with ad-pr first."

Phase 2 — evaluate. Run the structured check and report each line:

gh pr checks <num>
gh pr view <num> --json mergeable,mergeStateStatus,reviews,number,title,headRefName,baseRefName
gh api repos/:owner/:repo/pulls/<num>/comments

Findings format (pass / warn / fail):

CI status:           <pass | pending | fail>
Fresh-context review: <pass | warn — none found>
Linked task / ADR:   <pass | warn — none>
Unresolved comments: <pass | warn — N unresolved>
Mergeability:        <pass | dirty | blocked | behind>

Fresh-context review check — scan for either a file under .agentic/reviews/* whose name references the PR's commit range or number, or a gh pr view --json reviews entry with state: APPROVED.

Linked task / ADR — scan commit message bodies under <base>..HEAD and the PR body for task-NNNN, ADR-NNNN, spec-NNNN, #<issue>, Closes, Fixes.

Unresolved comments — count entries from gh api that lack a resolved flag or carry an in-progress thread state.

Phase 3 — decision. Apply the bar:

  • CI failing → hard stop. Refuse to merge until CI is green, unless the user explicitly overrides ("merge anyway"). On override, log a loud warning that this is a deliberate CI-failing merge and the responsibility is the user's. Per ADR-0025 §3, even the hard gate yields to explicit user authorization, but the override is surfaced visibly.
  • CI pending → ask the user: wait for CI, or proceed anyway? Default = wait.
  • CI green + warnings (no fresh-context review / no linked task / unresolved comments) → surface each warning, ask the user to confirm the merge, proceed on confirm.
  • All green → proceed.

State the decision back to the user before Phase 4 so they can interject.

Phase 4 — merge. Detect repo's allowed merge modes:

gh repo view --json mergeCommitAllowed,squashMergeAllowed,rebaseMergeAllowed

Decision tree:

  • Exactly one mode allowed → use it.
  • Multiple modes allowed → ask the user: "Repo allows squash / rebase / merge-commit. Pick one." Wait for their choice.
  • None allowed (rare) → surface the policy error and stop.

Run the merge:

gh pr merge <num> --squash --delete-branch

(replace --squash with --rebase or --merge per the chosen mode).

--delete-branch by default for feature branches (feat/*, fix/*, chore/*, docs/*, refactor/*). Skip --delete-branch if the source branch is a long-lived integration branch (e.g., cli, develop, release/*).

Capture and report the merge commit URL.

<output_contract> The output is a merged PR. The skill returns:

  • The merge commit URL.
  • A one-line summary (<count> commits merged into <base> via <mode>).
  • The list of warnings the user proceeded past (if any), for the audit trail. </output_contract>

Next

  • After merge: pull the latest base locally (git checkout <base> && git pull).
  • If the merge surfaced a recurring drift: ad-drift for systemic gaps, or update WORKFLOW.md §10 / §11.
  • If the merge closed a task: confirm the task file's Status is done and the Notes log captures the merge commit URL.
  • If the merge shipped a binding decision worth recording: ad-adr (three-criteria rule).

Read the full file on GitHub · 103 lines

Files

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.

Changes

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.

  1. 2mo ago First seen · 103 lines · 134 tokens per session scan A d836a1f4c53b

Subscribe to this mod's changes

ad-merge is a skill published in the GitHub repository CorridorTech/PoseCap (265 stars, last pushed 3d ago), licensed Apache-2.0. It adds 134 tokens to every session and 1,306 once invoked, about $0.0005 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-08-30.

Related

Other skills, from other repositories

pr

Draft a PR body from OMC's paper trail — the smallest visual that proves the change, evidence consumed from the verify protocol (never re-collected), reversibility from the ADR test on the diff, glossary language throughout.

Yeachan-Heo/oh-my-claudecode · 47 tokens

merge-batch

Prepare and merge an owner-selected PR batch with contributor credit and exact-candidate admission. Use for a pasted PR list; combined focused validation is diagnostic, and every actual landing still requires its applicable checks and authorization.

diegosouzapw/OmniRoute · 46 tokens

otto-pr-review-loop

Run Polly and OCR on a PR until all findings settle.

omnigent-ai/omnigent · 17 tokens

engram-branch-pr

PR creation workflow for Engram following the issue-first enforcement system. Trigger: When creating a pull request, opening a PR, or preparing changes for review.

Gentleman-Programming/engram · 37 tokens

github-contributor

A step-by-step guide for contributing code, tests, documentation, or build changes to open-source projects you do not maintain. It explains how to prepare a pull request that follows the project’s rules and is easier for maintainers to review.

daymade/claude-code-skills · 105 tokens

revdiff

Review diffs, files, and documents with inline annotations in a TUI overlay, or answer questions about revdiff usage, configuration, themes, and keybindings. Opens revdiff in agterm/tmux/zellij/herdr/kitty/wezterm/cmux/ghostty/iterm2/emacs-vterm, captures annotations, and addresses them. Works in git, hg, and jj repos…

umputun/revdiff · 248 tokens