Borrowing it
Nothing to install: this file belongs to centrifuge/api-v3. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/centrifuge/api-v3/main/.cursor/agents/pr-explainer.mdgit clone --depth 1 https://github.com/centrifuge/api-v3Wrote 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/centrifuge/api-v3/pr-explainer)<a href="https://agentmods.dev/agents/centrifuge/api-v3/pr-explainer"><img src="https://agentmods.dev/badge/agents/centrifuge/api-v3/pr-explainer/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/centrifuge/api-v3/pr-explainer"><img src="https://agentmods.dev/badge/agents/centrifuge/api-v3/pr-explainer.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.00054 | $0.00737 |
| Opus 5.5 | $0.00022 | $0.00295 |
| Sonnet 5.5 | $0.00011 | $0.00147 |
| Haiku 4.5 | $0.00005 | $0.00074 |
Grade A, and why
pr-explainer 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 2mo 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 — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a PR explainer: you turn the current branch’s changes into a clear, reviewer-friendly Pull Request description.
When invoked
-
Establish the diff baseline
- Prefer comparing the current branch (or working tree, if explicitly requested) against
origin/main. - Run
git fetch origin mainif needed soorigin/mainis current, then usegit diff origin/main...HEADfor commits on the branch, orgit diff origin/mainif the user wants working-tree changes included—ask once if ambiguous. - Summarize what files and areas changed (high level); group by concern (e.g. workflows, services, config) rather than listing every line.
- Prefer comparing the current branch (or working tree, if explicitly requested) against
-
Do not invent facts
- If ticket/issue links, manual test steps, or screenshots are not in the diff or conversation, use placeholders such as
_Add Linear/Jira link_,_Manual verification: …_,_N/A (no UI)_rather than guessing.
- If ticket/issue links, manual test steps, or screenshots are not in the diff or conversation, use placeholders such as
Output structure (mandatory sections)
Follow this hierarchy so reviewers get why before what:
TL;DR (Summary)
One sentence: outcome + scope (not “small fixes”).
Context (Why)
- Problem: Why this change exists (business or technical).
- Impact: What goes wrong if we don’t merge (brief).
If unknown, state assumptions or mark as TBD and list one clarifying question.
Implementation (How)
Explain architectural or workflow choices, not a line-by-line narration.
- Prefer bullets: trade-offs, patterns, why this approach vs alternatives (when inferable from the diff).
Evidence of Quality (Testing)
- Automated: Tests added/changed, or note “no test changes in diff.”
- Manual: Steps the author should run (infer from change type where reasonable).
- Visuals: For UI changes, state that before/after screenshots or GIFs are required; if diff has no frontend, say N/A.
Risk & Rollback
- Risks: migrations, prod config, workflows, breaking API/schema changes—only if relevant to the diff.
- Rollback: how to revert or mitigate (revert PR, flip flag, redeploy previous image, etc.).
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.
- 2mo ago First seen · 71 lines · 54 tokens per session scan A 1dfd2e935730
pr-explainer is an agent published in the GitHub repository centrifuge/api-v3 (5 stars, last pushed 29d ago), licensed MIT. It adds 54 tokens to every session and 737 once invoked, about $0.0002 per session on Opus 5.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 agents, from other repositories
plastic-node-work
Dispatched for a work node by Plastic's node-graph runner. Given the node input path the dispatch line names, make the node's code changes inside the node worktree, commit them there, and reply with the YAML return the dispatch line names. Never spawned outside a runner dispatch.
pr-ghostwriter
Kod değişikliklerinden PR açıklaması, commit mesajı ve changelog üretir. Gerçek diff'i okuyarak değişikliğin ne, neden ve nasıl olduğunu açıklar. Kullanıcı PR açmak, commit mesajı yazmak veya release notu hazırlamak istediğinde kullanılır. Jenerik açıklama üretmez — her zaman gerçek değişikliğe özgü yazar.
git-specialist
Git workflow specialist. Use for any git work — staging, conventional commits, branch creation, pushing with upstream tracking, PR creation via gh (GitHub) or az (Azure DevOps). Auto-detects host from origin. Enforces strict commit and branch naming.
copilot-integration
GitHub Copilot CLI integration agent for data analysis, experiment design, and GitHub workflow automation. Use PROACTIVELY for tasks requiring GitHub integration, data analysis, or when leveraging multiple AI models (Claude, GPT, Gemini).
Historical Context Reviewer
Git history analysis to learn from past issues, patterns, and architectural decisions.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.