agentmods.dev

github-pr-acceptance

Instructions for accepting or merging a GitHub pull request so GitHub records it as merged. A pull request is a proposed set of code changes awaiting integration.

In plain words
What is it for?
Use it when a pull request must be merged into the repository's main branch and verified on GitHub.
Why use it?
It checks both local integration and GitHub's final pull request status, avoiding a merge that exists only in local history.

Skill for Claude CodeCodex

893 3mo ago A scan 39 tokens original MIT
View the source file friuns2/codex-mobile
Install

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.

agentmods
npx agentmods add skills/friuns2/codex-mobile/github-pr-acceptance
Any agent
npx skills add friuns2/codex-mobile --skill github-pr-acceptance
Clone the repo
git clone --depth 1 https://github.com/friuns2/codex-mobile

Made for: Claude Code, Codex.

Per session 39 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 433 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00039 $0.00433
Opus 5 $0.00019 $0.00217
Sonnet 5 $0.00008 $0.00087
Haiku 4.5 $0.00004 $0.00043

Measured 2d ago against content hash 7a81eefde15a, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

github-pr-acceptance 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 2d 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/github-pr-acceptance/SKILL.md · 48 lines

What it actually says

GitHub PR Acceptance

When To Use

Use this skill when the user explicitly asks to accept/merge a pull request on GitHub (not just locally).

Goal

Ensure the PR is shown as MERGED on GitHub, with mergedAt and mergeCommit populated.

Workflow

  1. Perform local integration first
  • Merge intended work into local main using repository merge rules.
  1. Push main to canonical remote
  • For this project, canonical remote is https://github.com/friuns2/codexUI.git.
  1. Verify PR state
  • Run:
    • gh pr view <number> --repo friuns2/codexUI --json state,mergedAt,mergeCommit,mergeStateStatus,url
  • If state is MERGED, stop.
  1. If still OPEN
  • If mergeStateStatus is DIRTY (common after rebase or cross-repo PR):
    • push reconciled branch to PR head ref.
    • if still open, create a no-content linkage merge commit on main against exact PR head SHA:
      • git checkout main
      • git merge --no-ff -s ours <pr-head-sha> -m "Merge pull request #<number> from <owner>/<branch>"
    • push main again.
  1. Final verification (mandatory)
  • Re-run gh pr view ... and confirm:
    • state: MERGED
    • mergedAt is non-null
    • mergeCommit is non-null

Notes

  • Local merge alone is not enough when user asks for GitHub acceptance.
  • Cross-repo PRs may remain open even after equivalent code lands if ancestry/linkage is missing.
  • If contributor attribution matters, avoid rewriting PR commit ancestry where possible.
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. 2d ago First seen · 48 lines · 39 tokens per session scan A 7a81eefde15a

Subscribe to this mod's changes

github-pr-acceptance is a skill published in the GitHub repository friuns2/codex-mobile (893 stars, last pushed 3mo ago), licensed MIT. It adds 39 tokens to every session and 433 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-30.

Code reviewGit and workflowai-agentsai-assistantai-coding-agentclaudecodexopenai
Related

Other skills, from other repositories

contacts

Manage contacts, communication channels, access control, and invite links.

vellum-ai/vellum-assistant · 14 tokens

gmail

Manage Gmail email — drafting, sending, organizing, filters, vacation replies, and inbox analysis.

vellum-ai/vellum-assistant · 20 tokens

app-builder

Build and edit small, personal visual tools and artifacts — dashboards, trackers, calculators, data visualizations, charts, simple landing pages, and slide decks the user wants for THEMSELVES. This is the right skill whenever the user asks to "visualize this," "make a chart," or "build an artifact" for their own use…

vellum-ai/vellum-assistant · 162 tokens

assistant-migration

Migrate from ChatGPT, Claude, OpenClaw, Hermes, Manus, and other AI assistants into Vellum by inspecting their data exports, conversation archives, files, prompts, custom instructions, memory, saved memories, tools, GPTs, workflows, integrations, and relationships, then mapping as much as safely possible into Vellum…

vellum-ai/vellum-assistant · 90 tokens

guardian-verify-setup

Set up channel verification for phone, Telegram, Slack, Discord, or email channels via outbound verification flow.

vellum-ai/vellum-assistant · 26 tokens

media-processing

Ingest and process media files (video, audio, image).

vellum-ai/vellum-assistant · 16 tokens