Borrowing it
Nothing to install: this file belongs to ReflexioAI/reflexio. 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/ReflexioAI/reflexio/main/.agents/skills/update-pr/SKILL.mdgit clone --depth 1 https://github.com/ReflexioAI/reflexioWrote 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/reflexioai/reflexio/update-pr)<a href="https://agentmods.dev/skills/reflexioai/reflexio/update-pr"><img src="https://agentmods.dev/badge/skills/reflexioai/reflexio/update-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.
<a href="https://agentmods.dev/skills/reflexioai/reflexio/update-pr"><img src="https://agentmods.dev/badge/skills/reflexioai/reflexio/update-pr.svg" alt="Reviewed on agentmods" width="80" 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.00071 | $0.01618 |
| Opus 5.5 | $0.00028 | $0.00647 |
| Sonnet 5.5 | $0.00014 | $0.00324 |
| Haiku 4.5 | $0.00007 | $0.00162 |
Grade A, and why
update-pr scanned grade A with 1 finding 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 26d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
<How the changes were verified — manual testing steps, automated tests run, curl commands, etc.> This is a copy
100% identical to update-pr — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 128 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PR Updater
Push follow-up changes to an existing PR and update its description to reflect the new work.
Workflow
Step 1: Pre-flight Checks
- Verify GitHub CLI authentication — run
gh api user --jq '.login'to confirm the CLI is authenticated. If this fails, the user needs to rungh auth loginfirst. - Find the existing PR — run
gh pr view --json number,title,body,url,baseRefName,stateto find the PR for the current branch. If no PR exists, abort and suggest using/create-prinstead. Check thestatefield — if it is notOPEN, abort and inform the user that the PR is already merged or closed. - Verify clean git state — run
git statusto ensure no uncommitted changes. If there are uncommitted changes, commit them directly — do NOT delegate to another skill or tell the user to commit first. - Sync submodules — check if
.gitmodulesexists first. If it does, rungit submodule update --init --recursive. If not, skip this step.
Step 2: Sync with Base Branch
Ensure the feature branch is up-to-date with the base branch to avoid merge conflicts:
- Fetch latest remote — run
git fetch origin <base-branch>(use the base branch from the PR metadata) - Check for divergence — run
git log HEAD..origin/<base-branch> --onelineto see if the base branch has new commits - Rebase if needed — if there are new commits on the base branch:
a. Run
git rebase origin/<base-branch>b. Resolve conflicts — if the rebase hits conflicts:- Read the conflicting files to understand both sides
- Surface the conflict to the user — show both sides and ask which version to keep. Do not silently resolve conflicts.
- Stage resolved files:
git add <file> - Continue:
git rebase --continue - Repeat until rebase completes
- Verify clean state — run
git statusto confirm no unresolved conflicts remain - Push the branch — run
git push. If the rebase changed history, usegit push --force-with-leaseinstead. If--force-with-leasefails, it means someone else has pushed to this branch. Fetch the remote branch (git fetch origin <branch>), inspect the divergence (git log HEAD..origin/<branch> --oneline), and ask the user how to proceed — they may need to integrate the other contributor's changes first.
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.
- 26d ago Changed a9177fd86d67
- 1mo ago First seen · 128 lines · 71 tokens per session scan A a5deb237bade
update-pr is a skill published in the GitHub repository ReflexioAI/reflexio (379 stars, last pushed today), licensed Apache-2.0. It adds 71 tokens to every session and 1,618 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). It is 100% identical to update-pr, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
update-pr
Update an existing pull request with new changes. Use when the user wants to update a PR, push follow-up changes to a PR, refresh a PR description, or sync a PR with latest commits. Triggers on: update pr, update-pr, update the pr, push to pr, refresh pr, sync pr, update pull request.
create-pr
Create high-quality pull requests via gh pr create. Use when the user wants to create a PR, submit a PR, open a pull request, submit for review, or push changes for review. Triggers on: create a pr, create-pr, submit a pr, open a pull request, submit for review, make a pr, gh pr create.
github
Full GitHub CLI control — issues, PRs, code reviews, repo management. Uses gh CLI with auth detection, rate limiting, and templates. Triggers on: github, issue, pull request, PR, code review, repo, branch, label, assignee, milestone, release, workflow, actions.
claude-smart
Codex-only — use when the user asks to run claude-smart commands in Codex, including claude-smart show, learn, restart, dashboard, clear-all, or slash-like requests such as /claude-smart:learn. In Claude Code the native plugin slash commands handle these; do not invoke this skill there.
auto-git-commiter
Use when automatically commit and push OpenClaw changes to GitHub. Enable continuous improvement with automatic versioning, changelogs, and deployment-ready commits. Use when working with auto git commiter.
agentic-jujutsu
Quantum-resistant, self-learning version control for AI agents with ReasoningBank intelligence and multi-agent coordination.