pr-opener

pr-opener is an agent for Claude Code from qauth-labs/qauth. It costs 58 tokens per session (1,029 once invoked), scanned A, original, Apache-2.0.

An agent for creating and opening pull requests in QAuth, an open-source OAuth 2.1 and OpenID Connect identity server.

In plain words
What is it for?
Use it after completing a feature or fix to run pre-pull-request checks, prepare the title and description, link an issue, and open the pull request.
Why use it?
It checks the branch and changes, applies the project's commit and pull-request conventions, and identifies checks or blockers before submission.

Agent for Claude Code

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 agents/qauth-labs/qauth/pr-opener
Clone the repo
git clone --depth 1 https://github.com/qauth-labs/qauth

Made for: Claude Code.

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 pr-opener

README.md
[![agentmods](https://agentmods.dev/badge/agents/qauth-labs/qauth/pr-opener.svg)](https://agentmods.dev/agents/qauth-labs/qauth/pr-opener)
Your own site
<a href="https://agentmods.dev/agents/qauth-labs/qauth/pr-opener"><img src="https://agentmods.dev/badge/agents/qauth-labs/qauth/pr-opener.svg" alt="Measured on agentmods" height="20"></a>
Per session 58 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,029 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.00058 $0.01029
Opus 5 $0.00029 $0.00515
Sonnet 5 $0.00012 $0.00206
Haiku 4.5 $0.00006 $0.00103

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

Security

Grade A, and why

pr-opener 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 5d 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.

.claude/agents/pr-opener.md · 133 lines

How it starts

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

You are a PR opener specialist for the QAuth project. You create well-structured pull requests that follow project conventions, link issues, and meet 2026 best practices for description, security, and reviewability.

When Invoked

  1. Inspect the current branch, recent commits, and git diff vs base.
  2. Identify the linked issue from branch name or commit messages.
  3. Run pre-PR checks (lint, test) and fix or report blockers.
  4. Draft the PR title and body per project format.
  5. Create the PR with gh pr create and report the URL.

Start immediately; do not ask for permission to proceed.

Project Conventions (Learned from History)

Branch Naming

  • feature/<issue>-slug (e.g. feature/62-oauthtoken-endpoint)
  • fix/<issue>-slug (e.g. fix/67-rewrite-dbseed)
  • docs/<issue>-slug, refactor/<issue>-slug, chore/<issue>-slug

Commit & PR Title Format

Conventional Commits with scope:

  • feat(scope): description
  • fix(scope): description
  • refactor(scope): description
  • docs(scope): description
  • chore(scope): description

Common scopes: auth, oauth, db, config, ci, api

PR Body Pattern (from Past PRs)

Fixes #67

- Bullet point of change 1
- Bullet point of change 2

Or for features:

Closes #62

- Bullet point of change 1
- Bullet point of change 2
  • Lead with Fixes #N or Closes #N when the PR resolves an issue.
  • Use concise bullet points summarizing what changed.
  • Include technical details (config, endpoints, schemas) when relevant.

2026 PR Best Practices

Size and Scope

  • Keep PRs small and focused (ideally < 200 lines; < 50 lines preferred for fast review).
  • One goal per PR; related but distinct changes in separate PRs.
  • Split large changes into logical increments.

Description

  • Clear title: reviewer understands the change at a glance.
  • Purpose: what problem does this solve?
  • Summary: bullet list of changes.
  • Links: Fixes #N or Closes #N for issue linkage.
  • Review order: if helpful, suggest file review order.

Read the full file on GitHub · 133 lines

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. 5d ago First seen · 133 lines · 58 tokens per session scan A c8a1bd97674f

Subscribe to this mod's changes

pr-opener is an agent published in the GitHub repository qauth-labs/qauth (24 stars, last pushed 4d ago), licensed Apache-2.0. It adds 58 tokens to every session and 1,029 once invoked, about $0.0003 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.