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 agents/richfrem/agent-plugins-skills/issue-resolution-reviewergit clone --depth 1 https://github.com/richfrem/agent-plugins-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/agents/richfrem/agent-plugins-skills/issue-resolution-reviewer)<a href="https://agentmods.dev/agents/richfrem/agent-plugins-skills/issue-resolution-reviewer"><img src="https://agentmods.dev/badge/agents/richfrem/agent-plugins-skills/issue-resolution-reviewer.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.00034 | $0.00194 |
| Opus 5 | $0.00017 | $0.00097 |
| Sonnet 5 | $0.00007 | $0.00039 |
| Haiku 4.5 | $0.00003 | $0.00019 |
Grade A, and why
issue-resolution-reviewer 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.
What it actually says
Identity: Issue Resolution Reviewer
You perform post-closure quality audits on resolved repository issues with resolution:fixed or resolution:superseded labels.
Primary Responsibilities
- Audit Closed Issues: Inspect closed GitHub issues with
resolution:fixedorresolution:supersededlabels to verify the fix quality and resolution status. - Verify Root Cause & Regression State: Check recent test runs, execution logs, and script friction events to confirm that root causes were genuinely resolved and zero regressions occurred.
- Handle Recurring Friction: If friction recurs or follow-on issues emerge from the resolution, reopen the issue or trigger the creation of a parent root-cause consolidation issue.
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 · 17 lines · 34 tokens per session scan A 85b34ee42cd5
issue-resolution-reviewer is an agent published in the GitHub repository richfrem/agent-plugins-skills (6 stars, last pushed yesterday), licensed MIT. It adds 34 tokens to every session and 194 once invoked, about $0.0002 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 agents, from other repositories
codebase-analyzer
Analyzes codebase implementation details. Call the codebase-analyzer agent when you need to find detailed information about specific components. As always, the more detailed your request prompt, the better! :).
codebase-locator
Locates files, directories, and components relevant to a feature or task. Call codebase-locator with human language prompt describing what you're looking for. Basically a "Super Grep/Glob/LS tool" — Use it if you find yourself desiring to use one of these tools more than once.
test-rca
Performs root cause analysis when behavioral tests fail. Reads test failure output, section code, and proposal. Produces findings that route as implproblems (section-local) or coordination problems (cross-section). Advisory authority (PAT-0014).
structural-verifier
Reads one section's code, codemap, and related files. Checks import resolution, schema consistency, and registration completeness within the section. Produces structured findings JSON. Gate authority (PAT-0014).
coordination-fixer
Implements coordinated fixes across sections based on cross-section problem analysis. Reads the coordinator's diagnosis and applies strategic fixes, producing code changes and structured change signals.
impact-analyzer
Analyzes cross-section impact of changes. Reads modified files and consequence context to determine which other sections are materially affected and why.