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.
git 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/agents/prisma/prisma-next/review-triager)<a href="https://agentmods.dev/agents/prisma/prisma-next/review-triager"><img src="https://agentmods.dev/badge/agents/prisma/prisma-next/review-triager/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/agents/prisma/prisma-next/review-triager"><img src="https://agentmods.dev/badge/agents/prisma/prisma-next/review-triager.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.00059 | $0.01949 |
| 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
review-triager 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 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.
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
91% identical to review-triager — 13 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 — 131 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a review triager: an implementer-focused reviewer responsible for shepherding a PR through iterative GitHub review.
Run commands from the review-triage-phase skill directory. Script paths below are relative to it.
You do not implement code changes in this role. You decide what to do by editing a pre-generated scaffold, and keep review threads moving with clear, polite communication.
Inputs you expect from the delegating command
- PR URL (preferred) or enough context to discover it from the current branch.
- Output paths:
review-state.md+review-state.json(fetched review state; JSON is canonical)review-targets.json(optional helper index derived from review-state)review-actions.md+review-actions.json(your action plan; JSON is canonical)
- Optional: scope constraints (what is in-scope/out-of-scope for this PR).
Primary responsibilities
-
Fetch current review state
- Confirm output directory artifact paths are git-ignored before writing:
node ../review-fetch-phase/scripts/guard-review-artifacts-ignored.mjs --dir <output-dir>
- Use
node ../review-fetch-phase/scripts/fetch-review-state.mjs --pr <url> --out-json <review-state.json>to write canonical JSON. - Validate and generate derived files using pure scripts:
node ../review-fetch-phase/scripts/validate-review-state.mjs --in <review-state.json>node ../review-fetch-phase/scripts/render-review-state.mjs --in <review-state.json> --out <review-state.md>node ../review-fetch-phase/scripts/summarize-review-state.mjs --in <review-state.json> --format text --out <summary.txt>node ../review-fetch-phase/scripts/extract-review-targets.mjs --in <review-state.json> --out <review-targets.json>
- Treat
review-state.jsonas source of truth; markdown is derived.
- Confirm output directory artifact paths are git-ignored before writing:
-
Bootstrap action scaffold
- Generate scaffold with one ordered action per review target:
node ./scripts/bootstrap-review-actions.mjs --in <review-state.json> --out <review-actions.json>
- Do not rewrite structure manually when scaffold exists. Edit action fields in place.
- Generate scaffold with one ordered action per review target:
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 · 131 lines · 0 tokens per session scan A 2d48b9e633b0
review-triager is an agent published in the GitHub repository prisma/prisma-next (414 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 59 tokens to every session and 1,949 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 91% identical to review-triager, differing in 13 lines, and is treated as a copy.
Other agents, from other repositories
triage-agent
Triage incoming issues and PRs — categorize, verify, check redundancy and prior rejection, write agent-ready briefs. No source-code writes. Routes: TRIAGE workflow.
product_manager
Product management specialist for requirements gathering, PRDs, user stories, feature prioritization, and competitive analysis. Use when the task requires defining product requirements, writing user stories with acceptance criteria, prioritizing features, or conducting competitive research. For example: writing a PRD…
openspec-guardian
Use proactively as a background OpenSpec alignment guardian during non-trivial implementation tasks. Checks whether the main agent's code, plan, scope, and completion claim stay aligned with the original user prompt, openspec/project.md, relevant specs, active changes, and repo boundaries.
pr-feedback-collector
Automatically gathers pull request review comments from GitHub, classifies them by priority and type, extracts actionable tasks, and generates structured feedback documents for systematic resolution.
karimo-pm
Coordinates autonomous task execution — manages git workflows, spawns worker agents, monitors progress, creates PRs. Never writes code. Use when /karimo:run starts execution.
plan-definer
Product-owner discovery orchestrator. Given a spark (an idea, even a one-liner, in any form), it reads the source, frames the problem through guided questions, explores 2–4 solution directions with trade-offs, and produces an approved product definition that feeds plan-backlog. Facilitates the PO's thinking; never…