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 shikanime-labs/skills --skill sks-pr-reviewgit clone --depth 1 https://github.com/shikanime-labs/skillsWrote 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/shikanime-labs/skills/sks-pr-review)<a href="https://agentmods.dev/skills/shikanime-labs/skills/sks-pr-review"><img src="https://agentmods.dev/badge/skills/shikanime-labs/skills/sks-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/shikanime-labs/skills/sks-pr-review"><img src="https://agentmods.dev/badge/skills/shikanime-labs/skills/sks-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.00029 | $0.01178 |
| Opus 5 | $0.00015 | $0.00589 |
| Sonnet 5 | $0.00006 | $0.00236 |
| Haiku 4.5 | $0.00003 | $0.00118 |
Grade A, and why
sks-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 3d 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 — 126 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PR Review (sks-pr-review)
Review local diffs and GitHub PRs through the ponytail/YAGNI lens
(ponytail plugin skills; ponytail-review is the over-engineering-only
pass), enforcing shikanime review practice and repo conventions. Reports
only — never auto-commit/merge/fix. Uses jj, gh, and standard Hermes
tools.
The mechanics below (added-line security scan, independent fail-closed reviewer)
are distilled from requesting-code-review and adapted to the shikanime
human-gated flow: the agent posts findings and a verdict, a human approves.
When to Use
- "review this diff", "check before pushing", "review PR #N", "look at this PR"
- After a task touching 2+ files
- Before opening/merging a PR in shikanime/*
Prerequisites
- Inside a jj repo (colocated or jj-native)
ghauthenticated for PR-level interaction- Optional
ruff/eslint/tsc/go vet/pytest— skipped silently if absent
Procedure
1 — Scope. Diff + stat. Empty diff → tell user. >15k chars → split by file.
Command cheat-sheet: references/commands.md.
2 — High-level (Ponytail ladder). Per change:
- (1) needed? speculative need → flag deletion, not review polish;
- (2) already in codebase? reuse before reviewing a re-implementation;
- (3) root cause not symptom — fix where all callers route through, not in the one path the ticket named;
- (4) test strategy present and owned by the right unit?
Full ladder: the ponytail skill. Deliberate corner-cuts found here should
carry a ponytail: comment (ceiling + upgrade path) — ponytail-debt
harvests them.
3 — Security scan (added lines). Run references/security-scan.md. Any
match = blocking. Covers hard-coded secrets, shell/SQL injection,
eval/exec, unsafe deserialization, path traversal, XSS; plus auth
trust-boundary checks (Keycloak/JWKS timeout + client binding, NestJS/Prisma
type boundary).
4 — Independent verdict. Self-review checklist + a delegate_task reviewer
with only the diff (no shared context, fail-closed on non-JSON):
references/review-doctrine.md. passed false on any security/logic finding.
What ships with it
7 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.
- 3d ago Changed · +7 lines cc21d35c2356
- 12d ago First seen · 119 lines · 29 tokens per session scan A 03300760397b
sks-pr-review is a skill published in the GitHub repository shikanime-labs/skills (2 stars, last pushed yesterday), licensed Apache-2.0. It adds 29 tokens to every session and 1,178 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
issue
Use when starting a chain from a GitHub issue — turning an issue URL or number into a triaged, planned, dispatched, and reviewed pull request. Classifies the thread (bug → root-cause discipline, feature → plan chain, question → drafted reply), synthesizes a spec from the issue's own acceptance criteria, then runs the…
swarm-pr-review
Run a graph-guided, tool-augmented PR review using context packing, parallel exploration, mandatory repository-agnostic risk-family coverage with dispatch scaled to diff size and risk, independent reviewer validation, critic challenge, and metrics writeback. Use for deep pull request review with low false-positive…
include-test-files-that-assert-on-behavior-being-changed-in-decl
When delegating a task affected by this skill, include.
review
Use when the user wants code assessed rather than changed — "review PR 88", "is this branch ready to merge?", "look over my changes", "any problems with this diff?", "give me a code review", "what do you think of this PR?", "sanity-check this branch", "ship it?". Applies to a pull request or the current branch when…
magpie-pairing-self-review
Run a structured pre-flight self-review on local changes before opening a PR. Reads the diff against a configurable base (default: the merge base of HEAD and the upstream default branch), checks correctness, security, and project conventions, and returns a structured report to the developer. No state changes, no PR…
techdebt
Analyze Elixir/Phoenix technical debt — duplicates, refactoring opportunities, credo issues. Use when asked about code quality, cleanup, or what to improve.