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 tomzx/agents --skill pr-review-sendgit clone --depth 1 https://github.com/tomzx/agentsWrote 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/tomzx/agents/pr-review-send)<a href="https://agentmods.dev/skills/tomzx/agents/pr-review-send"><img src="https://agentmods.dev/badge/skills/tomzx/agents/pr-review-send/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/tomzx/agents/pr-review-send"><img src="https://agentmods.dev/badge/skills/tomzx/agents/pr-review-send.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.00022 | $0.00800 |
| Opus 5.5 | $0.00009 | $0.00320 |
| Sonnet 5.5 | $0.00004 | $0.00160 |
| Haiku 4.5 | $0.00002 | $0.00080 |
Grade A, and why
pr-review-send 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 22d 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 — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Send PR Review Comments
Posts individual PR review comments to GitHub by file and line number using the pr-comment.py script from the personal-automation repository.
should-post-to-github decides whether the comments are actually sent to GitHub (based on ~/.sdlc/config.yaml); when posting is disabled, the skill composes the comments and shows them for review instead.
Prerequisites
uvinstalledpr-comment.pyscript at$HOME/repos/git/personal-automation/others/pr-comment.py- GitHub authentication configured for the script
- Must run from within
$HOME/repos/git/personal-automation
Skill attribution (GitHub)
Before each pr-comment.py invocation, read github-post-attribution/SKILL.md and append the Posted with footer for SKILL_DIR = pr-review-send to the --comment text.
Communication guidelines (outbound text)
Before composing any text posted or drafted on the user's behalf, apply communication-guidelines/SKILL.md.
Steps
- Navigate to the automation directory:
cd $HOME/repos/git/personal-automation - Compose each review comment, applying
communication-guidelines/SKILL.mdfor concision (including the Skill attribution footer). - Decide whether to post: get the PR author with
ghx pr view <pr-number> --repo <owner>/<repo> --json | jq -r .author.login, then run~/.agents/scripts/should-post-to-github --repo "<owner>/<repo>" --author "<PR_AUTHOR>". If it exits 1, present the comments to the user and stop without posting. - If it exits 0, post a review comment (
--commentincludes main text plus Skill attribution footer):uv run $HOME/repos/git/personal-automation/others/pr-comment.py <owner>/<repo> <pr-number> \ --file <path/to/file.py> \ --line <line-number> \ --comment "<comment text>" - Repeat for each additional comment on different files or lines.
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.
- 22d ago Changed · +2 lines b8a5d8142cd9
- 24d ago Changed 653ffd19cbf1
- 27d ago Changed a75884b0fedf
- 28d ago Changed · +4 lines ed2c873dad32
- 1mo ago First seen · 66 lines · 22 tokens per session scan A f1458b261b81
pr-review-send is a skill published in the GitHub repository tomzx/agents (13 stars, last pushed yesterday), licensed MIT. It adds 22 tokens to every session and 800 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-09-03.
Other skills, from other repositories
review-implement-phase
Implements triaged review actions, commits focused fixes, and posts Done plus resolves threads. Use when the user wants only the implementation phase of the review-framework workflow.
github-pr-workflow
Prepare a GitHub pull request from a feature branch — branch hygiene, commit shape, title/body, verification notes, screenshots for UI work, and replies to review comments.
review-delta
Review only changes since last commit using impact analysis. Token-efficient delta review with automatic blast-radius detection.
github-contributor
A step-by-step guide for contributing code, tests, documentation, or build changes to open-source projects you do not maintain. It explains how to prepare a pull request that follows the project’s rules and is easier for maintainers to review.
hero-diff-highlight
A dark code editor reveals a red deletion then a green addition with a soft pulse. Function: PR / code-change explainer.
git-pr-workflows-git-workflow
Guide changes through code checks, testing, commits, and pull request preparation. Use when coordinating a complete Git workflow and verifying readiness for collaboration.