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/Smirnov-Labs/claude-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/smirnov-labs/claude-skills/pr-utilities)<a href="https://agentmods.dev/plugins/smirnov-labs/claude-skills/pr-utilities"><img src="https://agentmods.dev/badge/plugins/smirnov-labs/claude-skills/pr-utilities/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/smirnov-labs/claude-skills/pr-utilities"><img src="https://agentmods.dev/badge/plugins/smirnov-labs/claude-skills/pr-utilities.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
pr-utilities 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 5d 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-utilities",
"description": "Pull request tools — watching-pr-bot-reviews waits for and reads the automated reviewers (Codex, the Architecture/SAR review, CI) with prbots and gives a CLEAN/FIX/BLOCK/PENDING verdict for HEAD; /pr-fix drives a PR to clean by fixing feedback, pushing, and waiting with prbots",
"source": "./",
"strict": false,
"skills": [
"./skills/watching-pr-bot-reviews",
"./skills/pr-fix"
]
}What it installs
The manifest is a name and a version. 2 skills travel with it, and installing the plugin installs all of them — 251 tokens a session between them. Each is measured on its own page, and each can be installed alone.
What ships with it
1 file beside marketplace.json#pr-utilities 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.
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.
- 5d ago Changed · +1 lines dd3ebe6679c5
- 1mo ago First seen · 9 lines scan A a2110dcbb8b0
pr-utilities is a plugin published in the GitHub repository Smirnov-Labs/claude-skills (6 stars, last pushed 2d 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-09-03.
Other plugins, from other repositories
hunch
A git-native reasoning graph of decisions, bugs, and invariants for your codebase — queried and enforced at reasoning time. Adds the hunch MCP tools plus /hunch:capture, /hunch:heal, /hunch:why, /hunch:fix, /hunch:fragile.
git
Git workflow tools: commits, PRs, review inbox, checkout, and work triage.
ci-review
CI-optimized code review: multi-agent parallel review with confidence scoring and atomic GitHub PR review posting via gh api.
aigon
aigon. Aigon is a local, open-source, spec-first software-delivery orchestrator for coding agents. It takes a Git-backed feature spec through isolated implementation, cross-agent review, and merge—using the agents and subscriptions you already have.
diffctx
Selects the minimum code an LLM needs to review a git diff.
workflow
Code review and worktree workflow commands.