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/finos/git-proxy/address-reviewnpx skills add finos/git-proxy --skill address-reviewgit clone --depth 1 https://github.com/finos/git-proxyWhat 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.00012 | $0.01378 |
| Opus 5 | $0.00006 | $0.00689 |
| Sonnet 5 | $0.00002 | $0.00276 |
| Haiku 4.5 | $0.00001 | $0.00138 |
Grade A, and why
address-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 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 — 155 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Address review comments on a GitHub pull request.
Read AGENTS.md first. It is the canonical project guide for this repository.
The argument is a PR number (e.g. /address-review 98). If no number is given, ask the user.
Phase 1: Fetch and display comments
-
Save the current branch name:
git rev-parse --abbrev-ref HEAD -
Checkout the PR branch:
gh pr checkout <number> --detach -
Fetch review data (pick one):
REST (simple): Lists inline review comments; it does not include per-thread
resolvedstatus, so you cannot rely on it alone to skip resolved threads.
gh api repos/{owner}/{repo}/pulls/<number>/comments --paginate
GraphQL (for filtering resolved threads): Returns reviewThreads with isResolved, isOutdated, paths/lines, and nested comments—use this when step 5 must honor “already resolved.” Paginate with cursor (use null or omit for the first page; then pass reviewThreads.pageInfo.endCursor while hasNextPage is true).
gh api graphql -f query='
query($owner:String!, $repo:String!, $number:Int!, $cursor:String) {
repository(owner:$owner, name:$repo) {
pullRequest(number:$number) {
reviewThreads(first:100, after:$cursor) {
pageInfo { hasNextPage endCursor }
nodes {
isResolved
isOutdated
path
line
originalLine
comments(first:100) {
nodes {
databaseId
body
author { login }
createdAt
url
}
}
}
}
}
}
}' -F owner={owner} -F repo={repo} -F number=<number> -F cursor=<cursor>
First page: pass JSON null for cursor (see gh help api / your shell for how gh expects null). Later pages: set cursor to the previous response’s reviewThreads.pageInfo.endCursor until hasNextPage is false.
- Group comments by file. For each comment, extract:
id,path,line(ororiginal_line),body,user.login,in_reply_to_id(to detect threads). If you used GraphQL, mapdatabaseIdtoidand thread fields as needed. - Filter out threads that are already resolved (when using GraphQL method).
- Present a numbered summary to the programmer:
PR #<number> — <n> unaddressed review comments
1. <file>:<line> — @<author>: <first 80 chars of comment>
2. <file>:<line> — @<author>: <first 80 chars of comment>
...
If there are no unaddressed comments, say so and return to the original branch.
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 · 155 lines · 12 tokens per session scan A 954f62a5bf11
address-review is a skill published in the GitHub repository finos/git-proxy (243 stars, last pushed 2d ago), licensed Apache-2.0. It adds 12 tokens to every session and 1,378 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 skills, from other repositories
n8n-architect
Use when the user explicitly wants to create, edit, validate, sync, or troubleshoot n8n workflows, asks about n8n nodes or automation, or wants to use n8n-as-code in the current context root.
dependabot-batch
Use when reviewing Radar's weekly Dependabot PRs and replacing the safe, 72-hour-soaked updates with one changelog-vetted, tested PR.
test-radar
Use when building and testing Radar changes with the repository's real-instance smoke-test workflow.
visual-test
Use when visually testing Radar UI changes against a real Kubernetes cluster with Playwright screenshots.
qa-find-bugs
Drive the live product at https://dashboard.bex.co as a signed-in QA user (QAEMAIL / QAPASSWORD from .env), hunt real bugs across the hosting features, research each fix down to file:line, file the non-duplicate findings to the w6 board through /pm, and /ship the scheduled milestone. Use when the user asks to QA the…
pm
Inspect and maintain the repository's .pm workstreams, inbox notes, milestones, and tasks. Use when the user asks for PM board status or requests a supported board mutation such as creating, promoting, adding, or completing work.