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 commands/robofinsystems/robosystems/pr-reviewgit clone --depth 1 https://github.com/RoboFinSystems/robosystemsWrote 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/commands/robofinsystems/robosystems/pr-review)<a href="https://agentmods.dev/commands/robofinsystems/robosystems/pr-review"><img src="https://agentmods.dev/badge/commands/robofinsystems/robosystems/pr-review.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 | $0.00019 | $0.01600 |
| Opus 5 | $0.00010 | $0.00800 |
| Sonnet 5 | $0.00004 | $0.00320 |
| Haiku 4.5 | $0.00002 | $0.00160 |
Grade A, and why
pr-review 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 4d 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 — 120 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Review a pull request by gathering all PR metadata, diff, and review comments, then provide a comprehensive review summary.
Instructions
1. Identify the PR
The user may provide a PR URL, number, or nothing:
- URL provided (e.g.,
https://github.com/RoboFinSystems/robosystems/pull/577): Extract the repo and PR number - Number provided (e.g.,
577): Use the current repository - Nothing provided: Detect from the current branch using
gh pr view --json number,url— if no open PR exists for the current branch, ask the user which PR to review
2. Gather PR Data
Run these gh commands to collect all context:
# PR metadata + conversation comments in one call
gh pr view <NUMBER> --json number,url,title,body,author,state,isDraft,labels,comments,reviews,reviewDecision,latestReviews,reviewRequests,statusCheckRollup,mergeStateStatus,headRefName,headRefOid,baseRefName,additions,deletions,changedFiles,files,closingIssuesReferences,createdAt,updatedAt
# PR diff (the actual code changes)
gh pr diff <NUMBER>
# Inline review comments — no --json equivalent exists, so this call is still required
gh api repos/$(gh repo view --json nameWithOwner -q .nameWithOwner)/pulls/<NUMBER>/comments --paginate
Field notes:
reviewsnotreviewers—reviewersis not a valid field and errors.reviewDecisionis the single field that answers "has this been approved."commentscovers the top-level conversation, so no separateissues/<n>/commentscall is needed.closingIssuesReferencesgives the linked issue (needed for step 5's requirements check);filesgives per-file add/delete counts (needed for triaging a large diff);headRefOidis the HEAD SHA.- Keep
--paginatebare. Adding-q/--jqmakes gh emit one JSON document per page instead of a merged array, and--slurpcan't be combined with--jq. Pipe tojqafter the call, not through it.
3. Categorize Review Feedback
Organize all comments and checks into categories:
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.
- 4d ago First seen · 120 lines · 19 tokens per session scan A f0239ec22228
pr-review is a command published in the GitHub repository RoboFinSystems/robosystems (24 stars, last pushed yesterday), licensed Apache-2.0. It adds 19 tokens to every session and 1,600 once invoked, about $0.0001 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 commands, from other repositories
fill-event-triage
체결(fill) 이벤트, 특히 매도 체결 후 현금 재배치 판단을 read-only 트리아지로 자동 기동해 dry-run 제안을 남긴다. ROB-755.
crypto-alert-triage
Command "crypto-alert-triage" from mgh3326/auto_trader, covering crypto-alert-triage, 입력, 1. 맥락 복원 (반드시 이 순서), 2. 분석 and 3. dryrun 미리보기 (read-only).
akb-production-review
Review AKB production-governance docs and hooks.
feature
Post a feature to the Features Board on production and write tweets.
os-meeting
快速创建和管理AI团队会议.
csm-workledger
Show the surviving work-ledger entries across sessions.