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 agentmods add skills/friuns2/codex-mobile/github-pr-review-commentsnpx skills add friuns2/codex-mobile --skill github-pr-review-commentsgit clone --depth 1 https://github.com/friuns2/codex-mobileWhat 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 | $0.00037 | $0.00678 |
| Opus 5 | $0.00018 | $0.00339 |
| Sonnet 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 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 — 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.
- 2d 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 (893 stars, last pushed 3mo ago), licensed MIT. It adds 37 tokens to every session and 678 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-08-30.
Other skills, from other repositories
contacts
Manage contacts, communication channels, access control, and invite links.
gmail
Manage Gmail email — drafting, sending, organizing, filters, vacation replies, and inbox analysis.
app-builder
Build and edit small, personal visual tools and artifacts — dashboards, trackers, calculators, data visualizations, charts, simple landing pages, and slide decks the user wants for THEMSELVES. This is the right skill whenever the user asks to "visualize this," "make a chart," or "build an artifact" for their own use…
assistant-migration
Migrate from ChatGPT, Claude, OpenClaw, Hermes, Manus, and other AI assistants into Vellum by inspecting their data exports, conversation archives, files, prompts, custom instructions, memory, saved memories, tools, GPTs, workflows, integrations, and relationships, then mapping as much as safely possible into Vellum…
guardian-verify-setup
Set up channel verification for phone, Telegram, Slack, Discord, or email channels via outbound verification flow.
media-processing
Ingest and process media files (video, audio, image).