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/prisma/prisma-next/review-fetch-phasenpx skills add prisma/prisma-next --skill review-fetch-phasegit clone --depth 1 https://github.com/prisma/prisma-nextWrote 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/review-fetch-phase)<a href="https://agentmods.dev/skills/prisma/prisma-next/review-fetch-phase"><img src="https://agentmods.dev/badge/skills/prisma/prisma-next/review-fetch-phase.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.1 | $0.00039 | $0.00683 |
| Opus 5 | $0.00019 | $0.00342 |
| Sonnet 5 | $0.00008 | $0.00137 |
| Haiku 4.5 | $0.00004 | $0.00068 |
Grade A, and why
review-fetch-phase 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.
This is a copy
92% identical to review-fetch-phase — 2 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 — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Review Fetch Phase
Run only the state acquisition phase of the review-framework loop:
fetch canonical review state JSON (v2), validate it, and render all derived artifacts via scripts.
Run commands from this skill directory. All script paths below are relative to it.
Inputs
- Required:
- PR URL (for example:
https://github.com/OWNER/REPO/pull/123)
- PR URL (for example:
- Optional:
- output directory
If output directory is omitted, derive:
wip/reviews/<owner>_<repo>_pr-<number>/
Behavior
- Validate and parse PR URL, then compute deterministic paths:
<output-dir>/review-state.json<output-dir>/review-state.md<output-dir>/summary.txt<output-dir>/review-targets.json
- Ensure
<output-dir>exists. - Enforce artifact safety before generation (must be ignored by git):
node ./scripts/guard-review-artifacts-ignored.mjs --dir <output-dir>
- Run fetch script to produce canonical JSON:
node ./scripts/fetch-review-state.mjs --pr <PR_URL> --out-json <output-dir>/review-state.json
- Validate canonical JSON before deriving additional files:
node ./scripts/validate-review-state.mjs --in <output-dir>/review-state.json
- Render markdown from canonical JSON:
node ./scripts/render-review-state.mjs --in <output-dir>/review-state.json --out <output-dir>/review-state.md
- Generate text summary from canonical JSON:
node ./scripts/summarize-review-state.mjs --in <output-dir>/review-state.json --format text --out <output-dir>/summary.txt
- Extract deterministic triage targets for downstream bootstrap:
node ./scripts/extract-review-targets.mjs --in <output-dir>/review-state.json --out <output-dir>/review-targets.json
Target extraction includes:
- unresolved review threads
- pull-request reviews with body text
- issue comments with body text
Schema contract
review-state.jsonis canonical and must be schema version2.- No backward compatibility is provided for v1 artifacts.
- Derived artifacts (
review-state.md,summary.txt,review-targets.json) are regenerable from canonical JSON. - Review artifacts are generated files and must remain untracked in git.
What ships with it
9 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.
- package.json 555 B
- scripts/extract-review-targets.mjs 3.1 KB runs code
- scripts/fetch-review-state.mjs 16 KB runs code
- scripts/guard-review-artifacts-ignored.mjs 4.0 KB runs code
- scripts/render-review-state.mjs 7.5 KB runs code
- scripts/render-review-state.test.mjs 2.3 KB runs code
- scripts/review-artifacts.mjs 17 KB runs code
- scripts/summarize-review-state.mjs 6.0 KB runs code
- scripts/validate-review-state.mjs 2.3 KB runs code
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 First seen · 100 lines · 39 tokens per session scan A f48d64fcb3e2
review-fetch-phase is a skill published in the GitHub repository prisma/prisma-next (418 stars, last pushed 12d ago), licensed Apache-2.0. It adds 39 tokens to every session and 683 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 92% identical to review-fetch-phase, differing in 2 lines, and is treated as a copy.
Other skills, from other repositories
triage-contributor-pr
Triage open pull requests from external contributors to prisma/prisma and produce a per-PR verdict with evidence. Use when a maintainer asks to triage, evaluate, assess, or review the queue of incoming contributor PRs, to decide whether a fork PR is safe to run CI on, to check whether a PR is in scope for its version…
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.
review-triage-phase
Produces canonical review actions from fetched review state and renders action markdown. Use when the user wants only triage/action-planning for the review-framework workflow.
no-bare-casts
Writing as in TypeScript or TSX production code, modifying a file that contains a bare as cast, silencing a type error with a cast, encountering as unknown as, or reviewing a cast site.
record-gotchas
Capture surprises, workarounds, and rough edges hit while consuming the public surface of Prisma Next, Prisma Compute, or Prisma Postgres — anything a real user of these products would experience. Fires whenever an operator (or agent) writes a workaround, hits a surprising failure mode, or finds undocumented behaviour…
contrib-pr
Open a high-quality external contributor PR against prisma/orm. Use when the user is an outside contributor (not a Prisma maintainer) and wants to submit a change as a pull request from a fork. Encodes the contribution flow from CONTRIBUTING.md so the resulting PR passes review on the first round.