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/testdouble/han/post-code-review-to-prnpx skills add testdouble/han --skill post-code-review-to-prgit clone --depth 1 https://github.com/testdouble/hanWrote 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/testdouble/han/post-code-review-to-pr)<a href="https://agentmods.dev/skills/testdouble/han/post-code-review-to-pr"><img src="https://agentmods.dev/badge/skills/testdouble/han/post-code-review-to-pr.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.00088 | $0.01612 |
| Opus 5 | $0.00044 | $0.00806 |
| Sonnet 5 | $0.00018 | $0.00322 |
| Haiku 4.5 | $0.00009 | $0.00161 |
Grade A, and why
post-code-review-to-pr 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 yesterday.
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 — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.
When running a PR code review, follow the process outlined here.
Pre-requisites
- gh CLI: !
which gh 2>/dev/null || echo "not installed" - jq: !
which jq 2>/dev/null || echo "not installed"
If gh is not found, inform the user it must be installed and configured; if jq is not found, inform the user it must
be installed. In either case, immediately stop.
Project Context
- current branch: !
git branch --show-current 2>/dev/null || echo unknown - default branch: !
git symbolic-ref --short refs/remotes/origin/HEAD 2>/dev/null || echo unknown - changed files: !
gh pr diff --name-only 2>/dev/null || echo "no pr" - personal config directory: !
bash "${CLAUDE_PLUGIN_ROOT}/scripts/han-config-dir.sh" 2>/dev/null || echo "$HOME/.claude" - project .han/config.md: !
cat .han/config.md 2>/dev/null || echo ""
As your first action, use the Read tool on .han/config.md inside the personal config directory path above. A read
that returns no file is no personal configuration: continue silently. When that file or the project .han/config.md
probe supplies content, apply it per config-rule.md, which governs precedence
between the two files, relative-path resolution, and what to do with a file that reads but cannot be used.
Step 1: Validate PR State
If changed files is empty or reads no pr, or gh pr view --json number,url fails, inform the user no reviewable PR
exists for the current branch and stop.
Step 2: Run Code Review
Invoke the /code-review skill to perform the full code review. Pass along any user-provided focus areas or context
from the original arguments.
/code-review writes its report to a file and names the path in its closing message; it does not print the review into
the conversation. Capture that path — Step 3 reads the report from it. After /code-review completes, proceed
immediately to Step 3 — do not stop here.
Step 3: Offer to Post Review to GitHub
Ask the user whether they'd like to post the review to the PR on GitHub using AskUserQuestion with options "Yes, post
the review to GitHub" and "No, just the local review". If the user declines, proceed to Step 5.
What ships with it
4 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.
- yesterday First seen · 102 lines · 88 tokens per session scan A f1208f38a237
post-code-review-to-pr is a skill published in the GitHub repository testdouble/han (256 stars, last pushed 4d ago), licensed MIT. It adds 88 tokens to every session and 1,612 once invoked, about $0.0004 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-09-03.
Other skills, from other repositories
golden-chat-topics
Use when testing the goldenchattopics golden build.
golden-chat-single
Use when testing the goldenchatsingle golden build.
meta-tags-optimizer
Optimize title tags, meta descriptions, Open Graph, and Twitter cards for maximum click-through rate. Generates multiple A/B test variations with character counting and SERP preview. Use when asked to "optimize title tag", "write meta description", "improve CTR", "Open Graph tags", "fix my meta tags", "social media…
google-ads-audit
Google Ads account audit and business context setup. Run this first — it gathers business information, analyzes account health, and saves context that all other ads skills reuse. Trigger on "audit my ads", "ads audit", "set up my ads", "onboard", "account overview", "how's my account", "ads health check", "what should…
sxo
Search Experience Optimization (SXO) — the bridge between SEO and UX/CRO. Audits the full journey from the SERP click to the on-page goal: SERP click-through factors (title/meta/rich results that win the click), then post-click experience signals that keep users and drive conversions — above-the-fold relevance and…
elixir-idioms
OTP/BEAM patterns and Elixir idioms — GenServer, Supervisor, Task, Registry, pattern matching, with chains, pipes. Use when designing processes or debugging BEAM issues.