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 qodo-ai/qodo-skills --skill qodo-review-resolvergit clone --depth 1 https://github.com/qodo-ai/qodo-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/skills/qodo-ai/qodo-skills/qodo-review-resolver)<a href="https://agentmods.dev/skills/qodo-ai/qodo-skills/qodo-review-resolver"><img src="https://agentmods.dev/badge/skills/qodo-ai/qodo-skills/qodo-review-resolver/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/qodo-ai/qodo-skills/qodo-review-resolver"><img src="https://agentmods.dev/badge/skills/qodo-ai/qodo-skills/qodo-review-resolver.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 3 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 15 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
- medium Rogue Agent · line 34 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
- medium Excessive Agency · line 129 Skill allows unbounded resource consumption (API calls, storage, compute). Without rate limits or quotas, a compromised or misbehaving agent can cause denial-of-service or cost overruns.Fix: Set explicit rate limits, timeouts, and resource quotas for API calls, file operations, and compute. Implement circuit breakers for runaway loops.
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.00091 | $0.07057 |
| Opus 5.5 | $0.00036 | $0.02823 |
| Sonnet 5.5 | $0.00018 | $0.01411 |
| Haiku 4.5 | $0.00009 | $0.00706 |
Grade A, and why
qodo-review-resolver scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
description: Read or resolve a pull request's Qodo review using Qodo managed tools through MCP or the CLI — fetch structured status, reviewed commit SHA, and findings for ANY PR as JSON, with optional extended details an How it starts
The opening of the file, as written. The whole thing — 451 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Read & Resolve Findings
Description
Use Qodo managed tools to read a pull request's review session — its status, the commit that
was reviewed, and every finding with its resolution status — for any PR (yours or someone
else's). Request extended results when auditing citations or investigating a finding's supporting
evidence, location, dismissal, or review-run history. Reading alone is a valid use: stop after the read to report where a review stands or
what it flagged (e.g. to gate a merge on it being clean at head). To go further, resolve the
open findings in code, applying your own judgment (the review is a strong second opinion, not
gospel). Apply supported fixes when the user has authorized them; otherwise present your assessment
for selection. Run once (report + authorized fixes) or as a watch loop (resolve →
let Qodo re-review the new commit → repeat until clean). When separately authorized, record the outcome on the findings
you settled — mark-implemented for ones you fixed, dismiss for ones the user agreed to close
without a code change. That is what clears the merge-policy block those findings hold; skip it and
the review stays red until a human clicks through the PR. You still never post to the forge
yourself: the status tools write Qodo's review DB and Qodo reconciles the PR comments. (Plain
git/forge metadata reads — git rev-parse HEAD, gh pr view --json headRefOid — are fine and in
fact required for the freshness check below; the "don't scrape" rule is about qodo, not your shell.)
Prerequisites
- A connected QAR managed-tools MCP server or authenticated Qodo CLI exposes review-session tools.
- The exact PR URL and its current head SHA can be resolved without scraping review comments.
- Any finding-status write has explicit user authorization; code-fix authority or
autofixalone does not cover it.
Instructions
Choose the execution path
Use the connected QAR managed-tools MCP tools when the required review-session capability
is available; otherwise use the CLI path below. On MCP, read the host-provided descriptions,
inputSchema, and read-only/mutating annotations. The wire tools are
get-pr-review-findings (pr_url, optional extended), pr-review-dismiss, and
pr-review-mark-implemented; verify their live schemas before calling. Check isError
before structuredContent, including for a successful transport response. A truncated
finding result is incomplete, never a clean review.
What ships with it
4 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.
- 4d ago Changed · +5 lines 7659d4d0fa71
- 16d ago Changed · +21 lines · +5 tokens per session 7ff9931b59c7
- 24d ago Changed 7e76746c23ec
- 1mo ago Changed · +10 lines ed70198cf968
- 1mo ago Changed · +31 lines · +2 tokens per session 2a869710a92e
- 1mo ago Changed · -5 lines a1cf94edb929
- 1mo ago Changed · +6 lines 61ac74793ada
- 1mo ago First seen · 383 lines · 84 tokens per session scan A 146779b3b0bb
qodo-review-resolver is a skill published in the GitHub repository qodo-ai/qodo-skills (59 stars, last pushed today), licensed MIT. It adds 91 tokens to every session and 7,057 once invoked, about $0.0004 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
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…