agentmods.dev

review-fetch-phase

review-fetch-phase is a skill for Claude Code from prisma/orm. It costs 39 tokens per session (721 once invoked), scanned A, original, Apache-2.0.

A review workflow step that fetches the official state of a GitHub pull request review and creates readable summary files. A pull request is a proposed code change awaiting review.

In plain words
What is it for?
It helps collect review data for a specific pull request, validate it, and render JSON, Markdown, summaries, and review-target files.
Why use it?
It gives later review steps a validated, consistent record of the review instead of relying on scattered or stale information. It also places generated files in a protected working area.

Skill for Claude Code

Written for Claude Code: argument-hint in frontmatter.

not rated 48k +27 3d ago A scan 39 tokens original Apache-2.0
View the source file prisma/orm prisma.io
About the project

Prisma ORM is a Node.js and TypeScript database toolkit that lets applications work with databases through a programming interface instead of writing every query directly in SQL. Developers use it with databases including PostgreSQL, MySQL, MariaDB, SQL Server, SQLite, MongoDB, and CockroachDB. The catalogue add-ons provide agent rules, skills, hooks, agents, and other workflows for using Prisma.

prisma/orm · 47,606 stars · on GitHub · prisma.io

Install

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.

agentmods
npx agentmods add skills/prisma/orm/review-fetch-phase
Any agent
npx skills add prisma/orm --skill review-fetch-phase
Clone the repo
git clone --depth 1 https://github.com/prisma/orm

Made for: Claude Code.

Wrote 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.

agentmods badge for review-fetch-phase

README.md
[![agentmods](https://agentmods.dev/badge/skills/prisma/orm/review-fetch-phase.svg)](https://agentmods.dev/skills/prisma/orm/review-fetch-phase)
Your own site
<a href="https://agentmods.dev/skills/prisma/orm/review-fetch-phase"><img src="https://agentmods.dev/badge/skills/prisma/orm/review-fetch-phase.svg" alt="Measured on agentmods" height="20"></a>
Per session 39 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 721 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00039 $0.00721
Opus 5 $0.00019 $0.00360
Sonnet 5 $0.00008 $0.00144
Haiku 4.5 $0.00004 $0.00072

Measured 2d ago against content hash c1213303424e, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

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 2d ago.

The scan reads SKILL.md. This mod also ships 9 executable files (scripts/extract-review-targets.mjs, scripts/fetch-review-state.mjs, scripts/guard-review-artifacts-ignored.mjs, …), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

skills-contrib/review-fetch-phase/SKILL.md · 100 lines

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)
  • Optional:
    • output directory

If output directory is omitted, derive:

wip/reviews/<owner>_<repo>_pr-<number>/

Behavior

  1. 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
  2. Ensure <output-dir> exists.
  3. Enforce artifact safety before generation (the artifacts must stay untracked). In a git checkout the guard asks git directly; in a Jujutsu workspace with no git directory it accepts a directory under the workspace root's ignored wip/ tree:
node ./scripts/guard-review-artifacts-ignored.mjs --dir <output-dir>
  1. Run fetch script to produce canonical JSON:
node ./scripts/fetch-review-state.mjs --pr <PR_URL> --out-json <output-dir>/review-state.json
  1. Validate canonical JSON before deriving additional files:
node ./scripts/validate-review-state.mjs --in <output-dir>/review-state.json
  1. Render markdown from canonical JSON:
node ./scripts/render-review-state.mjs --in <output-dir>/review-state.json --out <output-dir>/review-state.md
  1. 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
  1. 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

Read the full file on GitHub · 100 lines

Files

What ships with it

10 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.

Changes

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.

  1. 2d ago First seen · 100 lines · 39 tokens per session scan A c1213303424e

Subscribe to this mod's changes

review-fetch-phase is a skill published in the GitHub repository prisma/orm (47,606 stars, last pushed 3d ago), licensed Apache-2.0. It adds 39 tokens to every session and 721 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-09-03.

cockroachdbjavascriptloggy-coreloggy-terminalmariadb
Related

Other skills, from other repositories

prisma-next-quickstart

Adopt Prisma Next into a new project, onto an existing database, or as the first move after a bootstrap tool dropped you into a scaffold. Use for "what can I do with Prisma Next", "what can I do next with Prisma", "where do I start", "what should I do first", "just ran createprisma", "createprisma", "npx…

prisma/prisma-next · 242 tokens

prisma-next-migration-review

Review what Prisma Next migrations will run on merge or deploy, render the migration graph, resolve concurrent / diamond-convergence conflicts, and configure environment refs for CI. Use for "what migrations are going to run", "what runs on deploy", merge conflict, diamond convergence, concurrent migrations, migration…

prisma/prisma-next · 107 tokens

prisma-next-supabase

Use Prisma Next with a Supabase project via @prisma-next/extension-supabase — wire extensions: [supabasePack], declare cross-space FKs to supabase:auth.AuthUser, author RLS policies (policyselect / policyupdate / @@rls, auth.uid() predicates), build db.ts with the supabase() factory, bind roles per request…

prisma/prisma-next · 244 tokens

create-pr

Creates a GitHub PR with a Linear-ticket-prefixed title and a decision-led, narrative description for prisma-next. Use when the user wants to create a pull request, open a PR, or submit changes for review.

prisma/prisma-next · 47 tokens

prisma-next-debug

Read a Prisma Next structured error envelope and route to the right recovery — code, domain, severity, why, fix, meta. Use for error, exception, my emit failed, my query won't typecheck, my query crashed, my migration won't apply, MIGRATION.HASHMISMATCH, BUDGET.ROWSEXCEEDED, BUDGET.TIMEEXCEEDED, RUNTIME.ABORTED…

prisma/prisma-next · 185 tokens

prisma-next-feedback

Hand a Prisma Next question or report off to the team — file a GitHub issue (bug or feature request), or route Q&A / design discussion / direct-team-contact to the Prisma Discord at pris.ly/discord. Use for bug, bug report, file an issue, report a bug, feature request, missing feature, this should be a feature, file…

prisma/prisma-next · 161 tokens