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.
npx agentmods add skills/runxhq/runx/github-pr-commentnpx skills add runxhq/runx --skill github-pr-commentgit clone --depth 1 https://github.com/runxhq/runxWrote 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/runxhq/runx/github-pr-comment)<a href="https://agentmods.dev/skills/runxhq/runx/github-pr-comment"><img src="https://agentmods.dev/badge/skills/runxhq/runx/github-pr-comment.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.00038 | $0.00703 |
| Opus 5 | $0.00019 | $0.00351 |
| Sonnet 5 | $0.00008 | $0.00141 |
| Haiku 4.5 | $0.00004 | $0.00070 |
Grade A, and why
github-pr-comment 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 — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub PR Comment
Post one bounded review comment to one known GitHub pull request. The skill is deliberately narrower than a general GitHub operator: it binds the exact repository, pull request, and comment body to a scoped provider operation, and closes only when provider evidence identifies and reads back the created note.
Use it after a review workflow has produced final wording and the operator wants
that exact note posted. Use issue-triage for analysis and drafting, and a
broader GitHub skill for other resource types. This skill never merges a pull
request; comment authority cannot be promoted into merge authority.
Composes
github-mcp-merge-pr#defaultgithub-mcp-pr-review-note#default
How it works
- Supply
owner/name, the exact pull-request number, exact comment body, and a stable idempotency key for that body. - The default
postrunner computes the body digest and admits the write only under a compatiblepr.commentgrant. - Native
provider.mutateposts underpr.comment; nativeprovider.readthen reads the returned comment ref underpr.read. Repository, PR number, comment ref, and body digest must match before completion. - The explicit
commentrunner preserves the separately human-gated bundledexamples/github-mcp-hero/review-notepath as the canonical MCP composition and deterministic harness surface. It is not live Connect evidence.
The separate merge-refused runner routes the same comment grant to the
bundled examples/github-mcp-hero/merge-pr denial fixture. It is an executable
authority test: a pr.merge request must seal as policy denied, never as a
backdoor merge path.
Stop conditions
- Stop when repository, pull-request number, body, or idempotency key is missing or changes after admission.
- The explicit
commentrunner stops when its human approval is absent or denied; the defaultpostrunner does not add that second gate. - Refuse a provider grant that does not resolve uniquely to
pr.comment. - Refuse a missing, ambiguous, wrong-provider, or under-scoped GitHub binding;
compatible local
gh, hosted connectors, and MCP transports all remain behind the same provider effect rather than a raw token or package HTTP client. - Do not treat mutation acceptance without an independent comment read, stable comment ref, and matching body digest as final readback.
- Never merge, close, label, or otherwise mutate the pull request beyond the exact comment.
What ships with it
3 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 First seen · 67 lines · 38 tokens per session scan A c9c0ce9bca47
github-pr-comment is a skill published in the GitHub repository runxhq/runx (84 stars, last pushed 3d ago), licensed Apache-2.0. It adds 38 tokens to every session and 703 once invoked, about $0.0002 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-09-03.
Other skills, from other repositories
merge-queue
Process the Refinery merge queue - collect agent work, detect and resolve conflicts, merge in dependency order, and verify integration.
dd-synthesis
Synthesize findings from multiple specialist agents into a coherent investment recommendation. Use when combining reports from 9+ specialist agents into a single decision document.
requesting-code-review
Use when completing tasks, implementing major features, or before merging to verify work meets requirements.
dd-report-format
Standard output format for due diligence analysis reports. Use when producing your final analysis to ensure consistency across all specialist agents.
dd-risk-scoring
Calculate weighted risk scores from specialist agent reports. Use when synthesizing multiple due diligence reports into an overall investment risk assessment.
dd-sourcing
Document sources properly for due diligence reports. Use when citing any external data, ensuring full traceability and auditability of findings.