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 nimble-giant/nimble-mold --skill pr-commentsgit clone --depth 1 https://github.com/nimble-giant/nimble-moldWrote 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/nimble-giant/nimble-mold/pr-comments)<a href="https://agentmods.dev/skills/nimble-giant/nimble-mold/pr-comments"><img src="https://agentmods.dev/badge/skills/nimble-giant/nimble-mold/pr-comments.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.00051 | $0.00733 |
| Opus 5 | $0.00026 | $0.00367 |
| Sonnet 5 | $0.00010 | $0.00147 |
| Haiku 4.5 | $0.00005 | $0.00073 |
Grade A, and why
pr-comments 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 7d 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 — 121 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Respond to PR Comments
Purpose
This command helps PR authors respond to review comments efficiently. It fetches PR details and comments using {{scm.provider}} CLI, enters plan mode to strategically address each comment, and executes the response plan with code changes and comment replies.
Command Name
pr-comments
Invocation Syntax
/pr-comments <pr-number>
/pr-comments <pr-url>
/pr-comments
Examples:
/pr-comments 1234- Address comments on PR #1234/pr-comments {{scm.base_url}}/owner/repo/pull/1234- Address comments using full URL/pr-comments- Address comments on current branch's PR (auto-detect)
Workflow Overview
Execute this workflow when the command is invoked:
- Fetch PR Information: Get PR details and all comments using {{scm.provider}} CLI {{- if .agent.plan_mode.enabled }}
- {{agent.plan_mode.enter}}: Present all comments and build response strategy {{- else }}
- Present all comments and build response strategy for user review {{- end }}
- Interactive Planning: For each comment, ask user how to respond
- Consolidate Plan: Present final response plan for approval
- Execute Plan: Make code changes and post replies as approved
Phase 1: PR Information Gathering
Step 1.1: Determine PR Number
If no PR number provided:
# Get current branch
CURRENT_BRANCH=$(git branch --show-current)
# Find PR for current branch
{{pr.find_for_branch}}
If URL provided, extract the PR number from the URL.
Step 1.2: Fetch PR Details
# Get PR information
{{pr.view}}
# Get PR comments (review comments on code)
{{pr.view_reviews}}
# Get detailed review comments
{{api.pr_review_comments}}
# Get general PR conversation comments
{{api.pr_conversation_comments}}
Step 1.3: Parse and Organize Comments
Group comments by:
- Review comments: Line-specific code feedback
- General comments: Overall PR discussion
- Resolved comments: Already addressed
- Pending comments: Require response
What ships with it
5 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.
- 7d ago First seen · 121 lines · 51 tokens per session scan A a0dc73f0f576
pr-comments is a skill published in the GitHub repository nimble-giant/nimble-mold (2 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 51 tokens to every session and 733 once invoked, about $0.0003 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
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…
write-pr
Reference standards for writing pull request titles and descriptions in the tldraw repository, plus the pre-flight comment sweep over the diff. Use as supporting guidance when another skill or workflow needs PR content standards, not as the user-facing create/update PR workflow.