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.
npx skills add charlesjones-dev/claude-code-plugins-dev --skill git-pr-codex-loopgit clone --depth 1 https://github.com/charlesjones-dev/claude-code-plugins-devWrote 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/charlesjones-dev/claude-code-plugins-dev/git-pr-codex-loop)<a href="https://agentmods.dev/skills/charlesjones-dev/claude-code-plugins-dev/git-pr-codex-loop"><img src="https://agentmods.dev/badge/skills/charlesjones-dev/claude-code-plugins-dev/git-pr-codex-loop/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/charlesjones-dev/claude-code-plugins-dev/git-pr-codex-loop"><img src="https://agentmods.dev/badge/skills/charlesjones-dev/claude-code-plugins-dev/git-pr-codex-loop.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.00075 | $0.01815 |
| Opus 5.5 | $0.00030 | $0.00726 |
| Sonnet 5.5 | $0.00015 | $0.00363 |
| Haiku 4.5 | $0.00007 | $0.00181 |
Grade A, and why
git-pr-codex-loop 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 1mo 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 — 161 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/git-pr-codex-loop - Codex Code Review loop
Positioning: Claude Code's native
/code-reviewcommand (with--fix,--comment, and the cloud "ultra" mode) now covers automated review-and-fix loops natively, with no external dependencies. This skill is specifically for repositories standardized on OpenAI's Codex Code Review bot, and remains the right tool for that cross-tool workflow.
You drive the current branch's pull request through Codex Code Review until the review is clean. The human makes the final merge decision; you never merge.
Prerequisites
- The GitHub CLI (
gh) is installed and authenticated (gh auth login). - Codex Code Review is enabled for the repository in Codex settings. With
Automatic reviews on, Codex reviews every new PR; otherwise you trigger a
review manually with
@codex review. Reviews post as the Codex bot (chatgpt-codex-connector). - Codex applies a
## Review guidelinessection from your repo'sAGENTS.mdwhen present, so project-specific review rules are honored automatically.
Process
Step 1: Open or find the PR
- Get the current branch:
git branch --show-current. If it ismainormaster, stop and tell the user to switch to a feature branch. - Look for an existing PR:
gh pr view --json number,url,state 2>/dev/null. If none exists, push the branch (git push -u origin HEAD) and open one withgh pr create --fill(write a real title/description if the change warrants it). Match the PR attribution style used by thegit-commit-push-prskill. - Capture the PR number and URL for the rest of the run.
Step 2: Monitor CI
Watch checks with gh pr checks --watch. If any check fails, fix the cause,
commit, push, and watch again. Do not continue while checks are red — Codex
reviewing a non-compiling PR is wasted.
Step 3: Monitor for the Codex review
When a review is requested — automatically on PR open, or by your @codex review reply — Codex first acknowledges with a 👀 (eyes) reaction on the
triggering post, then works. The 👀 means "received the request," not "done" —
do not act on it. Poll for the real outcome with gh pr view --comments, the
review-thread query below, and the reactions check below.
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.
- 1mo ago First seen · 161 lines · 75 tokens per session scan A 0e2271fc1244
git-pr-codex-loop is a skill published in the GitHub repository charlesjones-dev/claude-code-plugins-dev (35 stars, last pushed 6d ago), licensed MIT. It adds 75 tokens to every session and 1,815 once invoked, about $0.0003 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
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.
otto-pr-review-loop
Run Polly and OCR on a PR until all findings settle.
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.
verify-behavior
Verify or reproduce visible product behavior by driving the real UI with pi-computer-use's checked tools, requiring verified expect postconditions and durable state evidence for meaningful UI flows. Use when triage needs visual reproduction, implementation needs behavioral proof, review needs interactive confirmation…
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.
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…