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 ReflexioAI/claude-smart --skill update-prgit clone --depth 1 https://github.com/ReflexioAI/claude-smartWrote 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/claude-smart/update-pr)<a href="https://agentmods.dev/skills/reflexioai/claude-smart/update-pr"><img src="https://agentmods.dev/badge/skills/reflexioai/claude-smart/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/claude-smart/update-pr"><img src="https://agentmods.dev/badge/skills/reflexioai/claude-smart/update-pr.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Tool Misuse · line 36 Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).Fix: Validate all tool parameters against an allowlist. Reject dangerous parameter values (shell=True, --force, -rf /) and use safe defaults.
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.> Copies of this mod
1 near-identical copy found in the catalogue:
- update-pr — 100% identical, 0 lines differ
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/claude-smart (783 stars, last pushed yesterday), 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). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
smart-rebase
Smart partial rebase for squash-merge repositories. Auto-detect which commits to keep/drop when base branch was squash-merged into target. Use when: user says 'rebase', 'partial rebase', 'base already merged', 'smart rebase', or /smart-rebase. Not for: simple git rebase (the developer runs it — no skill executes…
connect-data-source
Connect Braintrust, Langfuse, LangSmith, Phoenix Cloud, or OpenTelemetry traces to Reflexio through its setup APIs. Guide the agent developer through traffic selection and field mapping, save and validate a draft, and return the Reflexio review link for frontend activation. Do not add an interaction-publish flow.
merge-prep
Pre-merge analysis and preparation. Analyzes source branch vs target branch: commit stats, conflict detection, file impact. Analysis-only v1 — outputs report + suggested commands, does not auto-merge. Use when: user says 'merge prep', 'pre-merge', 'merge analysis', or /merge-prep.
next-step
Change-aware next step advisor. Use when: user asks what to do next, workflow progression is unclear, session just started with dirty worktree. Not for: executing the suggested command (user decides), auto-loop decisions (hooks handle that). Output: findings-based suggestions or session summary with commit seed.
pr-comment
Post friendly review comments to a GitHub PR — prepare locally, preview, then submit as atomic review. Use when: posting code review comments, giving PR feedback, sending inline suggestions. Not for: reading existing reviews (use load-pr-review), creating PRs (use create-pr), PR status (use pr-summary).
git-investigate
Git history investigation. Use when: tracking code changes, finding where bugs were introduced, root cause analysis. Not for: code exploration (use code-explore), issue analysis (use issue-analyze). Output: history trace + root cause report.