Borrowing it
Nothing to install: this file belongs to friuns2/codex-mobile. 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/friuns2/codex-mobile/main/.agents/skills/github-pr-acceptance/SKILL.mdgit clone --depth 1 https://github.com/friuns2/codex-mobileWrote 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/friuns2/codex-mobile/github-pr-acceptance)<a href="https://agentmods.dev/skills/friuns2/codex-mobile/github-pr-acceptance"><img src="https://agentmods.dev/badge/skills/friuns2/codex-mobile/github-pr-acceptance/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/friuns2/codex-mobile/github-pr-acceptance"><img src="https://agentmods.dev/badge/skills/friuns2/codex-mobile/github-pr-acceptance.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.00039 | $0.00433 |
| Opus 5.5 | $0.00016 | $0.00173 |
| Sonnet 5.5 | $0.00008 | $0.00087 |
| Haiku 4.5 | $0.00004 | $0.00043 |
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 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.
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
- Perform local integration first
- Merge intended work into local
mainusing repository merge rules.
- Push
mainto canonical remote
- For this project, canonical remote is
https://github.com/friuns2/codexUI.git.
- Verify PR state
- Run:
gh pr view <number> --repo friuns2/codexUI --json state,mergedAt,mergeCommit,mergeStateStatus,url
- If
stateisMERGED, stop.
- If still
OPEN
- If
mergeStateStatusisDIRTY(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
mainagainst exact PR head SHA:git checkout maingit merge --no-ff -s ours <pr-head-sha> -m "Merge pull request #<number> from <owner>/<branch>"
- push
mainagain.
- Final verification (mandatory)
- Re-run
gh pr view ...and confirm:state: MERGEDmergedAtis non-nullmergeCommitis 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.
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.
- 2mo ago First seen · 48 lines · 39 tokens per session scan A 7a81eefde15a
github-pr-acceptance is a skill published in the GitHub repository friuns2/codex-mobile (978 stars, last pushed 1mo ago), licensed MIT. It adds 39 tokens to every session and 433 once invoked, about $0.0002 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.
Other skills, from other repositories
commit
Inspect git status, draft a commit message that matches the repo's style, and commit staged changes.
vellum-github-app-setup
Create and configure a GitHub App so the assistant can push commits, open PRs, and comment under its own bot identity. Use when the user wants the assistant to have its own GitHub identity, or when setting up git push access for the first time.
add-github
Add GitHub channel integration via Chat SDK. PR and issue comment threads as conversations.
baby-sit
Monitor a GitHub pull request until CI is green, diagnose failures, and rerun only evidence-backed flaky GitHub Actions jobs.
git-commit
Generate well-formatted git commit messages following conventional commit standards.
github
Use gh as the primary interface for GitHub data and actions. Keep this skill focused on basic operations and command safety, not maintainer triage strategy.