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/ValentinDutra/pr-mapWrote 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/plugins/valentindutra/pr-map/pr-map-plugin)<a href="https://agentmods.dev/plugins/valentindutra/pr-map/pr-map-plugin"><img src="https://agentmods.dev/badge/plugins/valentindutra/pr-map/pr-map-plugin/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/plugins/valentindutra/pr-map/pr-map-plugin"><img src="https://agentmods.dev/badge/plugins/valentindutra/pr-map/pr-map-plugin.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
pr-map 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.
What it actually says
{
"name": "pr-map",
"description": "Visualize a GitHub Pull Request as an interactive mind map and review it from the browser",
"version": "0.2.2",
"author": {
"name": "Valentin Dutra"
},
"repository": "https://github.com/ValentinDutra/pr-map",
"license": "MIT",
"keywords": [
"pull-request",
"code-review",
"knowledge-graph",
"github",
"dashboard"
]
}
What it installs
The manifest is a name and a version. 1 agent, 1 hook travel with it, and installing the plugin installs all of them — 89 tokens a session between them. Each is measured on its own page, and each can be installed alone.
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 · 18 lines scan A f3bef8b3293a
pr-map is a plugin published in the GitHub repository ValentinDutra/pr-map (9 stars, last pushed 3mo ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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 plugins, from other repositories
github-dev
Git and GitHub workflow skills for commits, PRs, code review, and comment resolution.
simplify
Review changed code for reuse, redundancy, and over-engineering, then apply fixes.
code-gauntlet
Adversarial code review for Claude Code: each GitHub PR or GitLab MR runs a gauntlet of up to seven specialist agents for bugs, security, tests and cross-file impact, and every finding must survive verification, a skeptical validator, and a blind challenge before it is posted.
pr-comments-resolver
Resolve unresolved PR/MR review comments across GitHub, GitLab, Bitbucket Cloud, and Azure DevOps.
github-triage
GitHub issue and PR triage with security-gated PR review workflow.
works-public
Independent static verification for immutable public GitHub commits.