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/DmitriyYukhanov/claude-pluginsWrote 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/dmitriyyukhanov/claude-plugins/issue-to-pr)<a href="https://agentmods.dev/plugins/dmitriyyukhanov/claude-plugins/issue-to-pr"><img src="https://agentmods.dev/badge/plugins/dmitriyyukhanov/claude-plugins/issue-to-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/dmitriyyukhanov/claude-plugins/issue-to-pr"><img src="https://agentmods.dev/badge/plugins/dmitriyyukhanov/claude-plugins/issue-to-pr.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
issue-to-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 7d 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": "issue-to-pr",
"version": "9.10.0",
"description": "Take a GitHub issue (bare, or tracked on a Project board) from triage to a merge-ready PR through a gated, worktree-isolated pipeline that scales its depth to the task and asks at most one batched question. The gates hold every run: design hardening, tests green, code review clean. Once you approve the PR in-session it squash-merges, reporting GitHub's own message if the merge is refused, then tears down the branch and worktree; a merge into anything but the default branch is reported as one, since that is where the issue's auto-close depends. The board card advances as work moves.",
"author": {
"name": "Dmitry Yuhanov"
}
}
What it installs
The manifest is a name and a version. 1 skill travel with it, and installing the plugin installs all of them — 138 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.
- 7d ago Changed 0e20bdd202d2
- 11d ago Changed d61f6881c07d
- 13d ago Changed 8ef3f367350a
- 14d ago Changed e30fdc030de9
- 17d ago Changed c5ee49705257
- 19d ago Changed 1ed32d154323
- 20d ago Changed 27058875c81f
- 23d ago Changed ac66c5750492
- 26d ago Changed 7d1c4a564e30
- 1mo ago First seen · 9 lines scan A 809a7b531836
issue-to-pr is a plugin published in the GitHub repository DmitriyYukhanov/claude-plugins (8 stars, last pushed 8d 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
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.
slack-changelog
Turns what changed in a release into a Slack changelog a non-technical audience can read — filtered to what they'd notice, one theme, one bullet per idea, no code vocabulary.
dev-tools-plugin
General developer tooling — read-only thinking and Q&A, git workflows, code hygiene, dependency management, and project documentation generation. Every skill is user-invoked only: Claude never starts a merge, an upgrade or a docs rewrite on its own.
sonu
Make your coding agent work like a senior teammate instead of an eager intern. /sonu:build writes every change in your style and test-first, then hands it back with the riskiest parts flagged before you review. /sonu:ship takes it from working tree to merged PR on its own — collecting every AI reviewer bot enabled on…
dark-factory
Curie's default dark factory agent: one labelled GitHub issue in, one reviewed pull request or one stated reason out. One agent reads the issue through the platform's getissue tool, pins acceptance criteria, plans, gets the plan reviewed by an Opus plan-reviewer subagent, writes a failing test where feasible, implemen.
privacy-guard
Keeps private infrastructure details out of public repositories. Ships the privacy-guard skill: session rules for what must never cross the public boundary, plus a per-repo pre-commit gate built on a gitignored local denylist and gitleaks. The denylist is never committed, so the hook is a no-op for external…