Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/quay/ai-helpersnpx agentmods add skills/quay/ai-helpers/prWrote 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/quay/ai-helpers/pr)<a href="https://agentmods.dev/skills/quay/ai-helpers/pr"><img src="https://agentmods.dev/badge/skills/quay/ai-helpers/pr.svg" alt="Measured on agentmods" height="20"></a>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.00043 | $0.01380 |
| Opus 5 | $0.00022 | $0.00690 |
| Sonnet 5 | $0.00009 | $0.00276 |
| Haiku 4.5 | $0.00004 | $0.00138 |
Grade A, and why
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 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.
How it starts
The opening of the file, as written. The whole thing — 205 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create Pull Request
Create a PR with the correct title format, description, and JIRA reference. This skill handles the full git workflow: validate, push, and PR creation.
IMPORTANT: Follow This Skill Exactly
Do not improvise. Follow the numbered steps in order. When steps fail, use the documented fallback ladder.
Critical Rules
- Always use a fork. Every push goes to a fork remote, every PR is a cross-fork PR. No exceptions — even if you have write access to upstream.
- Never push directly to upstream. Not even for "small" changes.
- Never skip pre-flight checks.
Step 0: Determine Auth Context
gh auth status
Determine your identity:
gh api user --jq .login 2>/dev/null
If that fails (403), you're running as a GitHub App:
gh api /installation/repositories --jq '.repositories[0].owner.login'
Record $GH_USER and $AUTH_TYPE (user-token / github-app / none).
Step 1: Pre-flight Checks
1a. Git configuration:
git config user.name && git config user.email
If missing, set from $GH_USER.
1b. Inventory remotes:
git remote -v
1c. Identify upstream and default branch:
gh repo view --json nameWithOwner,defaultBranchRef --jq '{nameWithOwner, defaultBranch: .defaultBranchRef.name}'
Record $UPSTREAM_OWNER/$REPO and $DEFAULT_BRANCH. Do not assume main.
1d. Verify changes exist:
git status && git diff --stat
Step 2: Validate PR Title
Title must match the CI-enforced regex (set via $PR_TITLE_PATTERN env var):
${PR_TITLE_PATTERN:-^(?:\[redhat-[0-9]+\.[0-9]+\] )?(?:PROJQUAY-[0-9]+|QUAYIO-[0-9]+|NO-ISSUE): [a-z]+(?:\([^)]+\))?: .+$}
bash .claude/scripts/validate-pr-title.sh "PROJQUAY-1234: fix(api): description here"
Step 3: Build Description
Read the template at .claude/templates/pr-description.md. Fill in:
- Summary: What this PR does
- Root Cause / Rationale: Why
- Changes: What changed
- Test Plan: How to verify
- JIRA Link:
${JIRA_BROWSE_URL:-https://redhat.atlassian.net/browse}/<TICKET-KEY> - Backport: Required or not
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.
- 2d ago First seen · 205 lines · 43 tokens per session scan A 83983cdd5731
pr is a skill published in the GitHub repository quay/ai-helpers (3 stars, last pushed 19d ago), licensed MIT. It adds 43 tokens to every session and 1,380 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-09-04.
Other skills, from other repositories
prowler-commit
Creates professional git commits following conventional-commits format. Trigger: When creating commits, after completing code changes, when user asks to commit.
gh-auth-isolation
Safely manage multiple GitHub identities (EMU + personal) in agent workflows.
comet-github
A routing guide for Comet-related GitHub work. It directs requests about pull requests, issues, CI failures, ideas, and fixes to the appropriate review or implementation process.
github-skill
Work with GitHub via the gh CLI — clone repositories, create/list/merge pull requests, create/list issues, and run any other gh command (API calls, workflow runs, releases, repo administration). List operations return parsed JSON.
codex-autoresearch
Run autonomous, measurable experiments in a Git repository: change one hypothesis, verify a numeric metric, keep improvements, and revert failures. Use when the user wants Codex to keep iterating toward a numeric target in the foreground or as a detached background run. Do not use for ordinary one-shot coding…
changelog-composer
Generates structured changelogs and release notes from git history and PRs, classifying breaking changes, features, fixes, performance, docs. Triggers on: "generate changelog", "write release notes", "what changed since", "prepare release", "release notes for", "diff since tag".