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/jv-vogler/skillsWrote 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/jv-vogler/skills/pr)<a href="https://agentmods.dev/plugins/jv-vogler/skills/pr"><img src="https://agentmods.dev/badge/plugins/jv-vogler/skills/pr/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/jv-vogler/skills/pr"><img src="https://agentmods.dev/badge/plugins/jv-vogler/skills/pr.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
pr 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",
"version": "1.0.0",
"description": "Use when working a pull request end to end: reviewing a diff locally for real bugs and design problems without posting anything to GitHub, and writing a PR description that explains why the change exists instead of narrating the diff file by file.",
"author": {
"name": "João Vogler",
"url": "https://github.com/jv-vogler"
},
"homepage": "https://github.com/jv-vogler/skills",
"repository": "https://github.com/jv-vogler/skills",
"license": "MIT",
"keywords": [
"pull-request",
"code-review",
"diff-review",
"github",
"git"
],
"skills": "./skills/"
}
What it installs
The manifest is a name and a version. 2 skills travel with it, and installing the plugin installs all of them — 143 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 · 21 lines scan A 6a6ba2cce20a
pr is a plugin published in the GitHub repository jv-vogler/skills (1 stars, last pushed 1mo 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
Skills for GitHub pull request workflows — creating PRs, addressing review feedback, and resolving threads.
han-github
Github specific extensions to the Han plugin for agentic planning and coding. Provides skills to post code reviews as PR comments, update a PR description with a consistent format, etc.
branch-recap
Tells you what your branch actually changed — what was done, why, and what deserves a second look, instead of the diff — then files the fixes into the commits they belong to.
autoimprove
Language-agnostic autonomous codebase improvement loop using isolated git worktrees. Every experiment runs on its own branch — main is never touched until a winning change is merged. Works with any language or framework.
review
PR review, interactive git diff annotation review, and writing style guide.
han-research
Pre-planning knowledge-work skills for the Han suite: understanding a problem before anyone commits to a plan. Home of research (research an open-ended question and end at an adversarially-validated recommendation), gap-analysis (compare two artifacts and report what is missing, incomplete, or conflicting), and…