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.
/plugin marketplace add DmitriyYukhanov/claude-pluginsnpx agentmods add plugins/dmitriyyukhanov/claude-plugins/issue-to-prgit 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.svg" alt="Measured on agentmods" 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 today.
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": "6.1.1",
"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; cleanup and the issue's auto-close follow only when the change landed in the default branch, and on any other base the run keeps the branch and says why. The board card advances as work moves.",
"author": {
"name": "Dmitry Yuhanov"
}
}
What it installs
The manifest is a name and a version. 2 skills, 1 hook travel with it, and installing the plugin installs all of them — 227 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.
- today Changed 25263688b0e4
- 4d ago First seen · 9 lines scan A d86620e1ad92
issue-to-pr is a plugin published in the GitHub repository DmitriyYukhanov/claude-plugins (7 stars, last pushed yesterday), 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
handbook-agent-spec-kit
Spec-driven development workflow system with structured phases: Requirements → Design → Tasks → Implementation.
handbook-discover
Discover and audit all plugins in a Claude Code marketplace with installation status, versions, and component breakdown.
handbook-dotnet
.NET development tools including automatic CSharpier formatting for C# files and dotnet run file support.
reflect
Better alignment with LLMs.
backend-architecture
Small, opinionated architecture guide for production backend services across languages and frameworks.
code-cleanup
Evidence-first cleanup of agent trajectory residue, dead islands, split-brain authority, stale dependencies, and unnecessary code across repositories.