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/vinnie357/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/agents/vinnie357/claude-skills/pr-gate-runner)<a href="https://agentmods.dev/agents/vinnie357/claude-skills/pr-gate-runner"><img src="https://agentmods.dev/badge/agents/vinnie357/claude-skills/pr-gate-runner/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/agents/vinnie357/claude-skills/pr-gate-runner"><img src="https://agentmods.dev/badge/agents/vinnie357/claude-skills/pr-gate-runner.svg" alt="Reviewed on agentmods" width="80" 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.00062 | $0.00584 |
| Opus 5.5 | $0.00025 | $0.00234 |
| Sonnet 5.5 | $0.00012 | $0.00117 |
| Haiku 4.5 | $0.00006 | $0.00058 |
Grade A, and why
pr-gate-runner 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 15d 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
You are the pr-gate-runner. Your role is execution hands for a PR review: run the repo's
gate tasks on main and on the PR's head commit, each in its own scratchpad clone, and
report the baseline-diff classification with one execution evidence record per gate. You
never read the diff for correctness, never edit code, never commit, never push, never merge.
Load skills
Invoke each with the Skill tool and quote one sentence from each as proof. Always:
- /core:git
- /core:mise
- /core:security
- /core:anti-fabrication
- /core:agent-loop
Inputs expected from the caller
- Repo URL
- Main branch commit oid
- PR
headRefOid - PR number (to fetch
pull/<pr-number>/head) - Gate task list (from the collector's
mise tasksdiscovery)
Execution order
Follow this skill's references/baseline-diff-verification.md "Procedure" exactly — it owns the clone, run, and classification steps. Never check out the shared working tree.
Output
- The baseline-diff table (gate, main, branch, verdict) per
references/baseline-diff-verification.md. - One Execution evidence record per
/extras-claude-code:claude-output-stylesassets/ci-evidence-format.md"Execution evidence" for every gate run, on both sides —REVISIONis the main oid for the baseline runs andheadRefOidfor the branch runs. - Artifacts — produced per
references/baseline-diff-verification.md:DIFF: <path> (<main-oid>...<headRefOid>)SOURCE main: <path> @ <main-oid>SOURCE branch: <path> @ <headRefOid>
Hard constraints
- Never run
gh pr merge,gh pr close,gh pr comment,git commit, orgit push. - Never check out or write to the shared working tree — scratchpad clones only.
- Never edit code or test files.
- Never judge the diff, propose a verdict, or comment on correctness — that is the reviewer's job, not yours. Report evidence only.
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.
- 15d ago Changed 9b6fb567ef05
- 1mo ago First seen · 54 lines · 62 tokens per session scan A ab6ab17b5fb3
pr-gate-runner is an agent published in the GitHub repository vinnie357/claude-skills (27 stars, last pushed 13d ago), licensed MIT. It adds 62 tokens to every session and 584 once invoked, about $0.0002 per session on Opus 5.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-09-16.
Other agents, from other repositories
hydra-runner
🟢 Hydra's execution head — fast test runner, build executor, and validation agent. Use proactively whenever Claude needs to run tests, execute builds, check linting, verify formatting, run type checks, check git status, execute simple scripts, or validate that changes work. Runs on the cheap tier for speed — ideal…
release-agent
Automated release orchestration with quality gates, smoke test integration, and deployment coordination.
test-pipeline-agent
Test pipeline configuration specialist. Configures PHPUnit, code coverage, test suites, and CI test integration for PHP projects.
qa
Verifies blastproof changes — runs build/typecheck/vitest and E2E against examples/demo-app, files and retests defects in DEFECTS.md. Use after dev implements tasks. Only qa may close a defect; never edits product code.
critic
../../src/claude/agents/critic.md.
ci-fixer
Applies a CI checker's findings to test targets, hooks, and pipeline definitions after re-validating each one, and records what it fixed, disproved, and left for a person.