Borrowing it
Nothing to install: this file belongs to BloomBooks/BloomDesktop. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/BloomBooks/BloomDesktop/master/.claude/skills/pr-comment-plan/SKILL.mdgit clone --depth 1 https://github.com/BloomBooks/BloomDesktopWrote 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/bloombooks/bloomdesktop/pr-comment-plan)<a href="https://agentmods.dev/skills/bloombooks/bloomdesktop/pr-comment-plan"><img src="https://agentmods.dev/badge/skills/bloombooks/bloomdesktop/pr-comment-plan/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/bloombooks/bloomdesktop/pr-comment-plan"><img src="https://agentmods.dev/badge/skills/bloombooks/bloomdesktop/pr-comment-plan.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.00092 | $0.00699 |
| Opus 5.5 | $0.00037 | $0.00280 |
| Sonnet 5.5 | $0.00018 | $0.00140 |
| Haiku 4.5 | $0.00009 | $0.00070 |
Grade A, and why
pr-comment-plan 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 1mo 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
PR comment plan
The job: gather the PR's unanswered review feedback into one Markdown document the developer
can read, decide on, and hand back. Nothing is replied to or changed in this skill; the
document is the deliverable. (Replying happens later, through reviewable-replies for
Reviewable threads or gh for GitHub threads.)
-
Pick the document name. If the user did not name one, ask, offering "append to or create
pr-comments.md" and, if that file already exists, a fresh unique name such aspr-comments-2.md. Ask this first and quickly so the user can leave while you work. -
Find the PR for the current branch with
gh(gh pr view --json number,url). If there is none, ask for a URL. -
Collect the comments that have no reply. Do not rely only on GitHub's
reviewThreads. Also read the PR's reviews and review bodies: Reviewable-imported comments and discussion summaries often appear only there, even when the review says it contains many unresolved comments. Treat those as part of the feedback to process. -
Write one block per comment, in this shape:
---------------------- ## Fred Flintstone review 3918647127 ### 1. foo should be bar Link: <https://reviewable.io/reviews/BloomBooks/BloomDesktop/7621#-On-YsWVBDGHZLABoBtc> Relevant code locations: bedrock.ts, line 52. What they said: | The foo here should be bar, shouldn't it? <-- verbatim quote; never paraphrase Evaluation: Bar wouldn't be bad, and the change is cheap. The complication is that we already have a bar. Action Proposals: 1. Change foo to baz <-- the proposed one first 2. Change foo to bar2 3. Say that <reviewer> prefers to stick with foo. - Proposed Reply: "[<attribution tag>] "bar" is already in use, so I've changed to "baz"." <-- not chatty; state what you did or would do User Decision: <-- the developer fills this in later Reply: - [ ] Reply successfully posted (tick when posted to GitHub or Reviewable) -------------------Leave the
User Decision:andReply:lines empty; a later step in the process fills them. The proposed reply starts with the team attribution tag (TEAM-AGENTS.md, "Attribution"), since it will be posted under the developer's account.
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.
- 1mo ago First seen · 58 lines · 92 tokens per session scan A ab7a5fd53cdb
pr-comment-plan is a skill published in the GitHub repository BloomBooks/BloomDesktop (43 stars, last pushed today), licensed MIT. It adds 92 tokens to every session and 699 once invoked, about $0.0004 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-19.
Other skills, from other repositories
pr
Draft a PR body from OMC's paper trail — the smallest visual that proves the change, evidence consumed from the verify protocol (never re-collected), reversibility from the ADR test on the diff, glossary language throughout.
merge-batch
Prepare and merge an owner-selected PR batch with contributor credit and exact-candidate admission. Use for a pasted PR list; combined focused validation is diagnostic, and every actual landing still requires its applicable checks and authorization.
otto-pr-review-loop
Run Polly and OCR on a PR until all findings settle.
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.
github-contributor
A step-by-step guide for contributing code, tests, documentation, or build changes to open-source projects you do not maintain. It explains how to prepare a pull request that follows the project’s rules and is easier for maintainers to review.
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…