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 andyzengmath/soliton --skill pr-reviewgit clone --depth 1 https://github.com/andyzengmath/solitonWrote 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/andyzengmath/soliton/pr-review)<a href="https://agentmods.dev/skills/andyzengmath/soliton/pr-review"><img src="https://agentmods.dev/badge/skills/andyzengmath/soliton/pr-review/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/andyzengmath/soliton/pr-review"><img src="https://agentmods.dev/badge/skills/andyzengmath/soliton/pr-review.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00017 | $0.10351 |
| Opus 5 | $0.00009 | $0.05176 |
| Sonnet 5 | $0.00003 | $0.02070 |
| Haiku 4.5 | $0.00002 | $0.01035 |
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 9d 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 — 886 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PR Review Skill
You are the orchestrator for Soliton PR Review. Follow these steps exactly.
Note the current time as reviewStartTime — you will need it for reviewDurationMs in the output metadata.
Step 1: Input Normalization
Determine the invocation mode from the target argument.
Mode A: Local Branch (no argument provided)
If no target argument was provided (or --branch flag was used):
-
Verify git repository:
git rev-parse --is-inside-work-treeIf this fails, output:
Error: Not in a git repositoryand STOP. -
Get current branch:
git branch --show-currentStore as
headBranch. -
Detect base branch: Try these in order until one exists:
git rev-parse --verify main 2>/dev/null && echo "main" git rev-parse --verify master 2>/dev/null && echo "master" git rev-parse --abbrev-ref origin/HEAD 2>/dev/null | sed 's|origin/||'Store the first successful result as
baseBranch.Validate branch names: Both
baseBranchandheadBranchmust match^[a-zA-Z0-9._\-/]+$(valid git ref characters only). If not, output:Error: Invalid branch name.and STOP. -
Gather the diff:
git diff ${baseBranch}...HEADStore as
diff. -
Check for empty diff: If
diffis empty, output:No changes detected on current branch vs ${baseBranch}.and STOP. -
Gather file list:
git diff --name-only --diff-filter=ACDMR ${baseBranch}...HEADParse each line into a
FileChangeentry. For each file, determine status from the diff filter:- A = added, C = copied, D = deleted, M = modified, R = renamed
-
Gather commit messages:
git log ${baseBranch}..HEAD --onelineStore as
prDescription(used as context for review agents). -
Construct ReviewRequest:
ReviewRequest { source: 'local' baseBranch: <detected base branch> headBranch: <current branch> diff: <full unified diff> files: <FileChange array from step 6> prDescription: <commit messages from step 7> config: <see Step 2 for config resolution> }
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 9d ago First seen · 886 lines · 17 tokens per session scan A 3ea9f2f18e52
pr-review is a skill published in the GitHub repository andyzengmath/soliton (1 stars, last pushed 2mo ago), licensed MIT. It adds 17 tokens to every session and 10,351 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-31.
Other skills, from other repositories
pr-review
Address feedback left on a GitHub pull request: fetch unresolved review threads, make agreed Elixir/Phoenix code fixes, reply, and resolve. Use for a PR URL/number or reviewer comments. NOT for pre-PR review, findings triage, or CI monitoring.
phx-pr-review
Address feedback left on a GitHub pull request: fetch unresolved review threads, make agreed Elixir/Phoenix code fixes, reply, and resolve. Use for a PR URL/number or reviewer comments. NOT for pre-PR review, findings triage, or CI monitoring.
resolve-pr-comments
Evaluate, fix, answer, and reply to GitHub pull request review comments and conversation comments. Handles both change requests (fix or skip) and reviewer questions (explain using reasoning recalled from past Claude Code transcripts). Use when the user asks to "resolve PR comments", "fix review comments", "address PR…
fetch-pr-comments
Fetch and summarize review feedback and conversation from a GitHub PR (unresolved review threads, review bodies, and PR conversation comments) without making changes. Use when the user asks to "fetch PR comments", "show PR comments", "check PR for unresolved comments", "list review comments", "what comments are on the…
reply-to-pr-threads
Draft, confirm, and post replies to GitHub PR review threads. Handles per-category reply formatting, re-fetches thread resolution state so auto-resolved threads are skipped, and posts via GraphQL. Use when the user asks to "reply to PR threads", "post PR thread replies", or "draft PR reply messages".
reply-to-pr-conversation
Draft, confirm, and post a single conversational reply to GitHub PR conversation comments (issue comments). The reply addresses all tracked items in one natural-prose message. Use when the user asks to "reply to PR conversation", "post PR conversation replies", or "draft PR conversation messages".