Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add DmitriyYukhanov/claude-plugins/plugin install issue-to-prWrote 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/skills/dmitriyyukhanov/claude-plugins/run)<a href="https://agentmods.dev/skills/dmitriyyukhanov/claude-plugins/run"><img src="https://agentmods.dev/badge/skills/dmitriyyukhanov/claude-plugins/run.svg" alt="Measured on agentmods" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00138 | $0.03409 |
| Opus 5 | $0.00069 | $0.01705 |
| Sonnet 5 | $0.00028 | $0.00682 |
| Haiku 4.5 | $0.00014 | $0.00341 |
Grade A, and why
run 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 2d 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.
How it starts
The opening of the file, as written. The whole thing — 171 lines — stays where its author put it; the contents beside it link to each section on GitHub.
issue-to-pr — issue → merge-ready PR pipeline
Gated flow: the gates block, the depth between them scales to the tier. Scripts own the
mechanics (S/ = ${CLAUDE_PLUGIN_ROOT}/scripts/, R/ = references/), you own judgment.
One todo per step.
Hard rules (never violate)
- New task = new branch in its own worktree (
S/worktree.sh ensure), cut from the resolved base. All work happens there; never two tasks in one tree. - Merge is gated on explicit in-session approval, runs ONLY in the main session, via
S/worktree.sh merge— never a baregh pr merge, never on the turn the PR opens. - Ask contract: three moments,
--grillreshapes the first (R/autonomy.md) — (1) Step 4: ONE batchedAskUserQuestionif the ledger has open items, or the grill in its place, (2) the merge gate, (3) a hard stop. Decide everything else yourself and log it (see below). - Stage with explicit paths (
git add path1 path2); nevergit add -A/., which sweeps in whatever the project keeps untracked. Conventional Commits. TDD (failing test first) for any logic. Write multi-line code with the Write tool — a Bash heredoc breaks on an apostrophe inside the body. - Humanizer runs on 100% of human-facing text (report, PR body, UI strings > 1–2 words) regardless of tier — not code/logs/commit subjects. Don't claim "green/passing" without the command output. Don't ask what a script or the code can answer.
- Check before you lean on it: a claim about anything outside this repo gets looked up before you build on it, and ledgered either way (
R/autonomy.md).
Config, tier, ask contract
- Config (
.claude/issue-to-pr/config.md, optional): you read it at Step 0 and resolve the base from it (R/configuration.md), in the main checkout — it is gitignored and absent in the worktree. Gate commands come from it, or from you at Step 6. Built in:code-review(Step 7),simplifyandverify(Step 8). Companions (if installed, else inline):superpowers:*,/cross-review,humanizer,ponytail:*,mattpocock-skills:grilling—R/companions.md. - Tier (
R/tier-matrix.md): you pick it at Step 1,standardunless the issue argues otherwise; it routes research depth, design, review level/passes and report length. - Autonomy (
R/autonomy.md, read once at Step 0): the ledger of judgment calls you keep in context and render into the report + PR body — the ask contract is above.
What ships with it
7 files beside SKILL.md 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.
- 2d ago Changed · -9 lines 33814d405ea6
- 6d ago First seen · 180 lines · 138 tokens per session scan A ec7a9a0cde6b
run is a skill published in the GitHub repository DmitriyYukhanov/claude-plugins (7 stars, last pushed yesterday), licensed MIT. It adds 138 tokens to every session and 3,409 once invoked, about $0.0007 per session on Opus 5. 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 skills, from other repositories
top-design
Create award-winning, immersive web experiences at the level of Awwwards-featured agencies. Use when the user mentions "Awwwards quality", "make my site stunning", "scroll animations", "parallax storytelling", "cinematic web design", "portfolio site", or "brand experience". Also trigger when elevating a standard…
design-everyday-things
Apply foundational design principles: affordances, signifiers, constraints, feedback, and conceptual models. Use when the user mentions "why is this confusing", "affordance", "error prevention", "discoverability", "human-centered design", "mental model", "mapping", "seven stages of action", "users keep making…
traction-eos
Implement the Entrepreneurial Operating System (EOS) to align vision and execution across a company. Use when the user mentions "EOS", "Entrepreneurial Operating System", "V/TO", "quarterly rocks", "Level 10 meetings", "accountability chart", "IDS process", "my company feels chaotic", "we keep having the same…
create-app
Guided journey from a raw app idea to a validated, cleanly architected first version that ships on a sustainable cadence. Orchestrates ten skills phase by phase - lean-startup, design-sprint, clean-architecture, domain-driven-design, clean-code, pragmatic-programmer, system-design, ios-hig-design, 37signals-way…
create-business
Guided journey from raw idea to a validated, positioned, priced business with a chosen beachhead. Orchestrates ten skills phase by phase - jobs-to-be-done, mom-test, design-sprint, lean-startup, good-strategy-bad-strategy, blue-ocean-strategy, obviously-awesome, hundred-million-offers, monetizing-innovation…
clean-architecture
Structure software around the Dependency Rule: source code dependencies point inward from frameworks to use cases to entities. Use when the user mentions "architecture layers", "dependency rule", "ports and adapters (hexagonal)", "onion architecture", "screaming architecture", "where should business logic go"…