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 skills add eaglesakura/agent-skills --skill fix-github-pr-commentgit clone --depth 1 https://github.com/eaglesakura/agent-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/skills/eaglesakura/agent-skills/fix-github-pr-comment)<a href="https://agentmods.dev/skills/eaglesakura/agent-skills/fix-github-pr-comment"><img src="https://agentmods.dev/badge/skills/eaglesakura/agent-skills/fix-github-pr-comment/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/skills/eaglesakura/agent-skills/fix-github-pr-comment"><img src="https://agentmods.dev/badge/skills/eaglesakura/agent-skills/fix-github-pr-comment.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.00178 | $0.03276 |
| Opus 5 | $0.00089 | $0.01638 |
| Sonnet 5 | $0.00036 | $0.00655 |
| Haiku 4.5 | $0.00018 | $0.00328 |
Grade A, and why
fix-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 6d 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 — 317 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Fix GitHub PR Comment
既存 Pull Request 上のレビュー指摘を読み、コードを直し、コミットして push し、 GitHub 上で返信してスレッドを Resolved にする。Stacked PR の場合は後続 PR へ変更を伝搬する。
いつ使うか
- ユーザーが 既存 PR 全体 のレビュー指摘対応を依頼したとき
- ユーザーが 特定コメント / スレッド の修正を依頼したとき
- 「指摘を直して push まで」「Resolved にして」など、修正 + GitHub 返信 がセットのとき
いつ使わないか
- 返信文案だけ・コメント起草だけ →
github-comment-rule - コミットメッセージだけ →
git-commit-comment-rule - Stacked PR の rebase / sync / merge だけ →
gh-stack - 巨大 PR の分割・再スタック →
decompose-fat-pr-to-stacked-prs - 新規 PR 作成 →
/github.create-pull-request
役割分担
| 役割 | 参照先 |
|---|---|
| コミットメッセージ | git-commit-comment-rule（必読・必須） |
| GitHub 返信文案・署名 | github-comment-rule（必読・必須） |
| Stacked PR の伝搬 | gh-stack SKILL |
| ブランチ名・Issue 番号 | workspace-git-branch-rule |
| 本 SKILL | チェックアウト → 修正 → 検証 → コミット → push → 返信 → Resolved → 伝搬 |
開始時に同パッケージの git-commit-comment-rule と github-comment-rule を読む。
ハードルール
- 作業ツリーはクリーン必須: 未コミット変更（staged / unstaged / untracked で作業に干渉するもの）がある状態では checkout しない。エラーとして停止し、ユーザーに stash / commit / discard を促す。
- PR ブランチの最新 HEAD で作業: checkout 後、
originの tip と fast-forward 同期する。 - CI Success は待たない（ユーザーが明示指示した場合のみ待つ）。
- 破壊的 git は禁止:
reset --hard、clean -fdx、force push、履歴書き換えはしない（明示承認なし）。 - ステージは指名のみ:
git add ./git add -Aは使わない。 - Resolved は対応済みスレッドだけ: 修正・返信したスレッドのみ resolve する。未対応の指摘を resolve しない。
前提
ghが認証済み- 対象リポジトリの作業ディレクトリにいる（または
--repo owner/nameを明示） - Stacked PR 伝搬には
gh extension install github/gh-stackが必要 gh stackは非対話で呼ぶ（view --json、submit --auto等）。詳細はgh-stackSKILL
作業手順
0. 対象の特定
ユーザー入力から次を確定する。
| 項目 | 例 |
|---|---|
| PR 番号 / URL | #123, https://github.com/org/repo/pull/123 |
| スコープ | PR 全体 / 特定スレッド（URL・コメント ID・引用） |
| リポジトリ | カレント repo または --repo |
PR=123
gh pr view "$PR" --json number,title,headRefName,baseRefName,url
1. 作業ツリーの検証（Checkout 前）
if [ -n "$(git status --porcelain)" ]; then
echo "ERROR: Working tree is not clean. Commit, stash, or discard changes first."
exit 1
fi
What ships with it
1 file 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.
- 6d ago First seen · 317 lines · 178 tokens per session scan A 360943aa8aa9
fix-github-pr-comment is a skill published in the GitHub repository eaglesakura/agent-skills (2 stars, last pushed 5d ago), licensed MIT. It adds 178 tokens to every session and 3,276 once invoked, about $0.0009 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-05.
Other skills, from other repositories
review-implement-phase
Implements triaged review actions, commits focused fixes, and posts Done plus resolves threads. Use when the user wants only the implementation phase of the review-framework workflow.
engram-branch-pr
PR creation workflow for Engram following the issue-first enforcement system. Trigger: When creating a pull request, opening a PR, or preparing changes for review.
verify-behavior
Verify or reproduce visible product behavior by driving the real UI with pi-computer-use's checked tools, requiring verified expect postconditions and durable state evidence for meaningful UI flows. Use when triage needs visual reproduction, implementation needs behavioral proof, review needs interactive confirmation…
github-contributor
End-to-end playbook for shipping high-quality pull requests to open-source projects you don't maintain — discovery, CONTRIBUTING compliance, PR-size check, minimal-diff implementation, PR description with AI-assisted disclosure, conflict resolution, and post-submission maintainer interaction. Use whenever creating…
revdiff
Review diffs, files, and documents with inline annotations in a TUI overlay, or answer questions about revdiff usage, configuration, themes, and keybindings. Opens revdiff in agterm/tmux/zellij/herdr/kitty/wezterm/cmux/ghostty/iterm2/emacs-vterm, captures annotations, and addresses them. Works in git, hg, and jj repos…
oss-maintainer
Run an open-source project's issue/PR/release loop like a careful human maintainer — triage to root cause, absorb community PRs before duplicating them, gate every merge, ship honest releases, and thank the people doing your QA for free.