Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/prisma/prisma-nextnpx agentmods add skills/prisma/prisma-next/github-review-iterationWrote 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/prisma/prisma-next/github-review-iteration)<a href="https://agentmods.dev/skills/prisma/prisma-next/github-review-iteration"><img src="https://agentmods.dev/badge/skills/prisma/prisma-next/github-review-iteration/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/prisma/prisma-next/github-review-iteration"><img src="https://agentmods.dev/badge/skills/prisma/prisma-next/github-review-iteration.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.00060 | $0.01951 |
| Opus 5.5 | $0.00024 | $0.00780 |
| Sonnet 5.5 | $0.00012 | $0.00390 |
| Haiku 4.5 | $0.00006 | $0.00195 |
Grade A, and why
github-review-iteration scanned grade A with 1 finding 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 1mo 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- Do **not** disable TLS verification (no `GH_NO_VERIFY_SSL`, no custom curl flags). This is a copy
91% identical to github-review-iteration — 8 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 231 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub Review Iteration
Run an iterative PR review loop: fetch state → render/summarize → triage actions → implement (code + Done + resolve) → re-fetch until the PR has no remaining actionable items.
This skill is an orchestrator. It delegates:
- triage to
../review-triage-phase/agents/review-triager.md - implementation to
../review-implement-phase/agents/review-implementer.md
The orchestrator owns sequencing, handoff, and loop control. It does not perform triage or implementation directly when delegation is available.
Locating sibling skills and scripts
This skill depends on three sibling skills that live in the same parent directory:
../review-fetch-phase/— fetches and renders PR review state../review-triage-phase/— triages review threads into an action plan../review-implement-phase/— implements triaged actions and resolves threads
All script paths in this document are relative to this skill's directory. Use ../ to reach sibling skills. Do not search the workspace/repo for these files — they are part of the skills installation, not the project being reviewed.
Usage
This skill supports subcommands:
triage: fetch + triage into structured actionsimplement: execute the triaged actions and update statusiterate: looptriage→implementuntil clear (default)
/github-review-iteration iterate <PR_URL> [output-dir]
When output-dir is omitted, use the standard layout: wip/reviews/<owner>_<repo>_pr-<number>/ (derived from PR URL).
Example:
/github-review-iteration iterate https://github.com/OWNER/REPO/pull/123
Files written (deterministic layout)
Store artifacts under:
wip/reviews/<owner>_<repo>_pr-<number>/
Canonical artifacts:
review-state.json(canonical v2)review-actions.json(canonical v2)
Derived artifacts:
review-state.mdsummary.txt(or JSON summary)review-actions.mdapply-log.json(optional)
When you need a thin wrapper for path setup + standard script calls, run:
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.
- 1mo ago First seen · 231 lines · 60 tokens per session scan A 0e230acd3cf5
github-review-iteration is a skill published in the GitHub repository prisma/prisma-next (414 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 60 tokens to every session and 1,951 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). It is 91% identical to github-review-iteration, differing in 8 lines, and is treated as a copy.
Other skills, from other repositories
pr
Draft a PR body from OMC's paper trail — the smallest visual that proves the change, evidence consumed from the verify protocol (never re-collected), reversibility from the ADR test on the diff, glossary language throughout.
merge-batch
Prepare and merge an owner-selected PR batch with contributor credit and exact-candidate admission. Use for a pasted PR list; combined focused validation is diagnostic, and every actual landing still requires its applicable checks and authorization.
otto-pr-review-loop
Run Polly and OCR on a PR until all findings settle.
engram-branch-pr
PR creation workflow for Engram following the issue-first enforcement system. Trigger: When creating a pull request, opening a PR, or preparing changes for review.
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.
revdiff
Review diffs, files, and documents with inline annotations in a TUI overlay, or answer questions about revdiff usage, configuration, themes, and keybindings. Opens revdiff in agterm/tmux/zellij/herdr/kitty/wezterm/cmux/ghostty/iterm2/emacs-vterm, captures annotations, and addresses them. Works in git, hg, and jj repos…