Borrowing it
Nothing to install: this file belongs to friuns2/codex-mobile. 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/friuns2/codex-mobile/main/.agents/skills/github-pr-review-comments/SKILL.mdgit clone --depth 1 https://github.com/friuns2/codex-mobileWrote 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/friuns2/codex-mobile/github-pr-review-comments)<a href="https://agentmods.dev/skills/friuns2/codex-mobile/github-pr-review-comments"><img src="https://agentmods.dev/badge/skills/friuns2/codex-mobile/github-pr-review-comments/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/friuns2/codex-mobile/github-pr-review-comments"><img src="https://agentmods.dev/badge/skills/friuns2/codex-mobile/github-pr-review-comments.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00037 | $0.00678 |
| Opus 5.5 | $0.00015 | $0.00271 |
| Sonnet 5.5 | $0.00007 | $0.00136 |
| Haiku 4.5 | $0.00004 | $0.00068 |
Grade A, and why
github-pr-review-comments 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 2mo 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 — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub PR Review Comments
When To Use
Use this skill when the user asks to:
- review open GitHub PRs
- check PRs not opened by the repo owner
- identify bugs, regressions, or missing validation in a PR
- write review comments back to GitHub with
gh
Goal
Produce high-signal PR review findings and, when requested, post concise review comments with gh.
Review Standard
Default to a code review mindset:
- prioritize correctness bugs
- prioritize behavioral regressions
- prioritize compatibility and rollout risk
- prioritize missing validation where the blast radius is meaningful
- avoid low-value style commentary unless it masks a real bug
A review comment should only be posted if it says something concrete that could block, regress, or materially weaken the change.
Workflow
- Identify candidate PRs
- Prefer
gh pr list --repo friuns2/codexUI --state open. - If the user asks for PRs not by owner, filter out PRs whose author matches the repo owner.
- Gather PR context
- Read PR title, author, body, changed files, and commits:
gh pr view <number> --repo friuns2/codexUI --json ...
- Read the diff:
gh pr diff <number> --repo friuns2/codexUI
- Narrow attention to risky files and changed contracts.
- Form findings
- Each finding should answer:
- what can break
- why it can break
- where in the patch it comes from
- Prefer 0-3 real findings over a long weak list.
- Write comments when requested
- Use
gh pr comment <number> --repo friuns2/codexUI --body ... - Keep comments short, direct, and technical.
- One comment per distinct issue is preferred when the issues are unrelated.
Comment Style
Use a terse, high-conviction review style:
- direct
- unsentimental
- technical
- specific about the failure mode
Good pattern:
- Name the concern in one sentence.
- Explain the concrete breakage path.
- State what needs to be clarified, tested, or fixed before merge.
Avoid:
- excessive hedging
- praise padding
- long summaries of the PR before the issue
- vague “maybe consider” language when the risk is real
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.
- 2mo ago First seen · 97 lines · 37 tokens per session scan A 1757ccd4a9f8
github-pr-review-comments is a skill published in the GitHub repository friuns2/codex-mobile (978 stars, last pushed 1mo ago), licensed MIT. It adds 37 tokens to every session and 678 once invoked, about $0.0001 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-08-30.
Other skills, from other repositories
engineer-bot-getting-started
An onboarding guide for an engineering delivery assistant. It helps define a repository, the allowed level of access, and the work needed before reviewing a code change.
developer_pr_prep
Prepare branches, diffs, tests, and GitHub PR text from a conversation's code folder.
release
Release gentle-pi through GitHub and npm. Trigger: release, publish, npm publish, GitHub release, version bump.
gentle-ai-work-unit-commits
Plan commits as reviewable work units. Trigger: implementation, commit splitting, chained PRs, or keeping tests and docs with code.
openclaw-github-dedupe
Investigate a cluster of GitHub issues and PRs, determine canonical candidates, post duplicate/related status, preserve contributor credit, and execute cleanup actions. Supports autonomous mode for provided-link-only closeout, merge/fix follow-through, changelog, and post-merge issue/PR cleanup.
pr-triage
4-phase PR backlog management with audit, deep code review, validated comments, and optional worktree setup. Use when triaging pull requests, catching up on pending code reviews, or managing a backlog of open PRs. Args: 'all' to review all, PR numbers to focus (e.g. '42 57'), 'en'/'fr' for language, no arg = audit…