A procedure for preparing or updating pull requests, which are proposed changes submitted for review. It records the source-backed behavior changes, usage differences, migration notes, and exact revision range.

Use it to create PR descriptions, document API changes, compare revisions, and audit existing pull requests or historical changes.

It helps reviewers and users distinguish the actual change from inherited or unrelated work, and avoids making claims based only on current files or commit messages.

create-pr — Skill for Codex by moeru-ai/auv

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.

Any agent

npx skills add moeru-ai/auv --skill create-pr

Clone the repo

git clone --depth 1 https://github.com/moeru-ai/auv

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/moeru-ai/auv/create-pr/github.svg)](https://agentmods.dev/skills/moeru-ai/auv/create-pr)

Your own site

<a href="https://agentmods.dev/skills/moeru-ai/auv/create-pr"><img src="https://agentmods.dev/badge/skills/moeru-ai/auv/create-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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/moeru-ai/auv/create-pr"><img src="https://agentmods.dev/badge/skills/moeru-ai/auv/create-pr.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 48 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,670 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.

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.

Model	Per session	Once invoked
Fable 5.1	$0.00048	$0.01670
Opus 5.5	$0.00019	$0.00668
Sonnet 5.5	$0.00010	$0.00334
Haiku 4.5	$0.00005	$0.00167

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

Security

Grade A, and why

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

.agents/skills/create-pr/SKILL.md · 141 lines

How it starts

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

Create PR

Make the PR useful to both reviewers and downstream callers. Explain the final behavior, show exact calling changes, and preserve enough source context to audit those claims later. Follow the repository's AGENTS.md and PR template.

Establish the comparison

Identify the repository, PR or branch, base, and head. Record resolved commit SHAs in the disclosure. Use the actual PR diff, not every change since main.
For an open PR, compare its merge base with its head. For a merged or historical change, identify the reviewed or landed revision range and state which one you used. Do not infer historical behavior from today's working tree. A commit in Git is not proof of merge or release; use “head revision” unless that status was verified.
For stacked PRs, distinguish changes introduced here from changes inherited from the base. State dependencies and merge order. Recheck the base after an upstream merge; do not claim independence merely because a PR has its own URL.
Start with changed files, then inspect definitions, exports, and real callers at both revisions. Use git show, git diff, and targeted rg searches. PR prose and commit messages are context, not proof of an API contract.

Inventory caller-visible changes

Trace each changed contract across the layers that actually expose it: shared Rust types, driver capabilities, auv APIs, CLI arguments, Runner/Proto, and SDKs. Do not scan unrelated modules or invent obligations for untouched layers.

Always resolve these two surfaces explicitly for a caller-visible PR, even when one is unchanged:

CLI: inspect command definitions and dispatch, then show the exact command line before and after. Include subcommands, flags, defaults, stdin/stdout behavior, platform restrictions, and privilege requirements when relevant. A prose feature name such as “adds setup support” is not a CLI disclosure.
Protobuf / Runner API: inspect changed .proto files, generated bindings, Runner handlers, and their callers. Show exact RPC, message, field, enum, or behavior changes, including field numbers and compatibility implications. If the diff does not change this surface, say No Protobuf or Runner API changes; do not omit the surface or infer a wire change from CLI behavior.

Read the full file on GitHub · 141 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.

agents/openai.yaml 227 B

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.

11d ago Changed · +24 lines · +8 tokens per session be3d85239b12
1mo ago First seen · 117 lines · 40 tokens per session scan A 578c1c48db4e

Subscribe to this mod's changes

create-pr is a skill published in the GitHub repository moeru-ai/auv (115 stars, last pushed yesterday), licensed Apache-2.0. It adds 48 tokens to every session and 1,670 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-09-14.

Code review Git and workflow agent-memory agent-skills computer-use gui-automation os-automation phone-use

prismer-github

GitHub via gh CLI: PRs, issues, reviews, repos, auth.

Prismer-AI/PrismerCloud · 22 tokens

pr-body

A tool that reviews all commits on the current branch and creates or updates a pull request title and description. A pull request is a proposed code change submitted for review.

alibaba/anolisa · 68 tokens

pre-pr

Prepare a Honcho change for a pull request to plastic-labs/honcho. Invoke before opening a PR, when drafting a PR body, when asked if a branch is PR-ready, or when filling the pull request template. Checks the linked issue, required tests and docs, then writes Description / Proofs / Fixes.

plastic-labs/honcho · 69 tokens

create-pr