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 commands/nimble-giant/ailloy/pr-commentsgit clone --depth 1 https://github.com/nimble-giant/ailloyWrote 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/commands/nimble-giant/ailloy/pr-comments)<a href="https://agentmods.dev/commands/nimble-giant/ailloy/pr-comments"><img src="https://agentmods.dev/badge/commands/nimble-giant/ailloy/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 | $0.00000 | $0.02202 |
| Opus 5 | $0.00000 | $0.01101 |
| Sonnet 5 | $0.00000 | $0.00440 |
| Haiku 4.5 | $0.00000 | $0.00220 |
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 4d 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 — 336 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 GitHub 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 https://github.com/owner/repo/pull/1234- Address comments using full URL/pr-comments- Address comments on current branch's PR (auto-detect)
Workflow Overview
Claude must execute this workflow when the command is invoked:
- Fetch PR Information: Get PR details and all comments using GitHub CLI
- Enter Plan Mode: Present all comments and build response strategy
- 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
gh pr list --state open --head "$CURRENT_BRANCH" --json number,title
If URL provided, extract the PR number from the URL.
Step 1.2: Fetch PR Details
# Get PR information
gh pr view <pr-number> --json title,body,author,state,mergeable
# Get PR comments (review comments on code)
gh pr view <pr-number> --json reviewDecision,latestReviews
# Get detailed review comments
gh api repos/:owner/:repo/pulls/<pr-number>/comments --paginate
# Get general PR conversation comments
gh api repos/:owner/:repo/issues/<pr-number>/comments --paginate
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 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.
- 4d ago First seen · 336 lines · 0 tokens per session scan A 96ae708cde12
pr-comments is a command published in the GitHub repository nimble-giant/ailloy (10 stars, last pushed 3d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 2,202 tokens. 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 commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.