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/xbim08/awesome-claude-code-plugins/pr-issue-resolvegit clone --depth 1 https://github.com/xbim08/awesome-claude-code-pluginsWrote 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/xbim08/awesome-claude-code-plugins/pr-issue-resolve)<a href="https://agentmods.dev/commands/xbim08/awesome-claude-code-plugins/pr-issue-resolve"><img src="https://agentmods.dev/badge/commands/xbim08/awesome-claude-code-plugins/pr-issue-resolve.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.00014 | $0.01720 |
| Opus 5 | $0.00007 | $0.00860 |
| Sonnet 5 | $0.00003 | $0.00344 |
| Haiku 4.5 | $0.00001 | $0.00172 |
Grade A, and why
pr-issue-resolve 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 today.
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 — 172 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Analyze and Resolve Suggested Changes in GitHub Pull Request
Follow these steps to analyze suggested changes (e.g., review comments, inline suggestions, or requested modifications) in a GitHub Pull Request (PR) and resolve them efficiently. The goal is to review, understand, plan fixes, apply changes, test, and update the PR while maintaining code quality and collaboration.
Assume the PR reference is provided as $ARGUMENTS (e.g., a PR number or URL like #456 or https://github.com/repo/pull/456).
Use the GitHub CLI (gh) for all GitHub-related tasks, such as fetching PR details, comments, and updating the PR.
PLAN
-
Use
gh pr viewto get the PR details- Fetch the full PR title, description, base branch, head branch, labels, assignees, reviewers, and any linked issues.
- Note the current status (e.g., open, draft, merged) and any merge conflicts.
-
Fetch and review all comments and suggestions
- Use
gh pr comment listorgh apito retrieve all review comments, including inline suggestions (e.g., code diffs suggested in reviews). - Categorize comments:
- Suggestions for code changes (e.g., "Change this function to use async/await").
- Questions or clarifications (e.g., "Why did you choose this approach?").
- Bugs or issues (e.g., "This breaks on edge case X").
- Style/nitpicks (e.g., "Rename variable for clarity").
- Approvals or general feedback.
- Identify threaded discussions or resolved/unresolved comments.
- Use
-
Identify related dependencies or context
- Look for linked issues or other PRs (e.g., "fixes #123" or "depends on #789").
- Check if the PR is part of a larger epic, feature branch, or release.
- Review the diff: Use
gh pr diffto understand the changes introduced in the PR. - If suggestions reference external resources (e.g., docs, standards), verify them.
-
Ask clarification questions if needed
- If a suggestion is ambiguous, prepare questions for the reviewer (e.g., post them as replies in the PR).
- Examples: "Can you provide an example of the expected output?" or "Does this need to handle internationalization?"
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.
- today First seen · 172 lines · 14 tokens per session scan A abcf55d4b4e9
pr-issue-resolve is a command published in the GitHub repository xbim08/awesome-claude-code-plugins (10 stars, last pushed yesterday), licensed Apache-2.0. It adds 14 tokens to every session and 1,720 once invoked, about $0.0001 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-04.
Other commands, from other repositories
debate
The debate — Claude and Codex argue a design decision from opposite corners, you arbitrate.
remember
Save the current session to persistent context memory.
decide
Forces structured decision-making and creates an auditable Agent Decision Record (AgDR).
skip-reflect
Discard queued learnings without processing.
analyze-codebase
Generate comprehensive analysis and documentation of entire codebase.
claude-desktop-extension
This command provides the context necessary for Claude Code to create the Desktop Extension or .dxt file of an MCP.