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 yimwoo/hotl-plugin --skill pr-reviewinggit clone --depth 1 https://github.com/yimwoo/hotl-pluginWrote 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/yimwoo/hotl-plugin/pr-reviewing)<a href="https://agentmods.dev/skills/yimwoo/hotl-plugin/pr-reviewing"><img src="https://agentmods.dev/badge/skills/yimwoo/hotl-plugin/pr-reviewing/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/yimwoo/hotl-plugin/pr-reviewing"><img src="https://agentmods.dev/badge/skills/yimwoo/hotl-plugin/pr-reviewing.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.00038 | $0.02842 |
| Opus 5 | $0.00019 | $0.01421 |
| Sonnet 5 | $0.00008 | $0.00568 |
| Haiku 4.5 | $0.00004 | $0.00284 |
Grade A, and why
pr-reviewing 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 — 325 lines — stays where its author put it; the contents beside it link to each section on GitHub.
HOTL PR Review
Overview
Review a pull request end-to-end across 4 dimensions (description/ticket, code changes, code scan, unit tests) using parallel subagents. Produces a structured verdict report and optionally posts line-level comments on GitHub.
Announce: "Starting PR review. Detecting platform and fetching PR data..."
Output Contract
This skill produces a structured review report. The canonical schema is defined in
docs/contracts/pr-review-output.md. All platforms must emit every section in that
contract. Platform-specific rendering (tables, inline comments, etc.) is handled by
platform docs, not this skill.
Key rules from the contract:
- All 9 sections always present, even on BLOCK
- Dimension verdicts summarize sections; individual findings may have mixed severities
- Overall verdict derived from dimension verdicts, not individual findings
- The contract is mandatory even when platform-native findings are emitted before it
Step 1: Platform Detection & PR Fetching
Resolve the PR
- If the user provided a PR URL → parse org/repo and PR number from it
- If no URL → detect from current branch:
- Try
gh pr view --json number,title,body,baseRefName,headRefName,url→ if succeeds, use GitHub mode - Try
glab mr view→ if succeeds, use GitLab mode - If both fail → use local-only mode (git diff against base branch)
- Try
Platform Modes
| Platform | CLI | Mode | Capabilities |
|---|---|---|---|
| GitHub (public) | gh |
full | Local report + post review comments |
| GitLab | glab |
local-only | Local report only |
| Enterprise/VPN | none | local-only | Local report only (git diff fallback) |
Fetch PR Data
Full mode (GitHub):
gh pr view <number> --json title,body,baseRefName,headRefName,changedFiles,additions,deletions
gh pr diff <number>
GitLab mode:
glab mr view <number>
glab mr diff <number>
Local-only fallback:
git log --oneline main..HEAD
git diff main...HEAD
git diff --name-only main...HEAD
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 · 325 lines · 38 tokens per session scan A 74566b343002
pr-reviewing is a skill published in the GitHub repository yimwoo/hotl-plugin (26 stars, last pushed 2mo ago), licensed MIT. It adds 38 tokens to every session and 2,842 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
gentle-ai-collab-perfect
Trigger: contributing to Gentleman-Programming/gentle-ai as an external collaborator. Strict issue-first workflow, honest PR bodies, contributor-vs-maintainer scope, chained-PR strategy, verification protocol, docstring coverage. Load whenever the active repo is Gentleman-Programming/gentle-ai and any part of the…
branch-pr
Create Gentle AI pull requests with issue-first checks. Trigger: creating, opening, or preparing PRs for review.
work-unit-commits
Plan commits as reviewable work units. Trigger: implementation, commit splitting, chained PRs, or keeping tests and docs with code.
chained-pr
Trigger: PRs over 400 lines, stacked PRs, review slices. Split oversized changes into chained PRs that protect review focus.
ring:committing-changes
Commit changes with scope allowlist enforcement, atomic grouping, GPG-signed conventional commits, and trailer management. Detects the repo's PR-validation scope policy before proposing any message. Use when the user asks to commit or has changes ready to record. Skip when the working tree is clean or the user wants…
ring:opening-pull-requests
Open a GitHub Pull Request with automatic base branch detection, scope allowlist enforcement, PR template filling, and post-create base verification. Replaces ring:generating-pr-descriptions. Use after pushing a branch when ready to open a PR. Skip if the branch is not yet pushed or there are uncommitted changes …