resolve

resolve is a skill for Claude Code, Codex from OutlineDriven/odin-claude-plugin. It costs 44 tokens per session (3,135 once invoked), scanned A, original, Apache-2.0.

A workflow for handling feedback on code under review. It can classify comments, apply accepted changes locally with tests, or prepare a response explaining why a suggestion is not being accepted.

In plain words
What is it for?
Assess review comments, implement accepted fixes, test those fixes, ask for clarification, and draft pushback for disputed suggestions.
Why use it?
It separates valid issues from misunderstandings and keeps changes and replies local until they are ready. It does not post replies or trigger remote checks.

Skill for Claude CodeCodex

Written for Claude Code and Codex: shipped in a Claude Code plugin, but also agents/openai.yaml present.

Part of the odin-git plugin — 46 skills shipped together

Good fit Assess review comments, implement accepted fixes, test those fixes, ask for clarification, and draft pushback for disputed suggestions.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/outlinedriven/odin-claude-plugin/resolve
Install

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.

Any agent
npx skills add OutlineDriven/odin-claude-plugin --skill resolve
Clone the repo
git clone --depth 1 https://github.com/OutlineDriven/odin-claude-plugin

Made for: Claude Code, Codex.

Or install odin-git, the plugin that ships this one along with the rest of its 46 skills.

Wrote 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.

agentmods badge for resolve

README.md
[![agentmods](https://agentmods.dev/badge/skills/outlinedriven/odin-claude-plugin/resolve/github.svg)](https://agentmods.dev/skills/outlinedriven/odin-claude-plugin/resolve)
Your own site
<a href="https://agentmods.dev/skills/outlinedriven/odin-claude-plugin/resolve"><img src="https://agentmods.dev/badge/skills/outlinedriven/odin-claude-plugin/resolve/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.

agentmods 80×15 button for resolve

Your own site · 80×15
<a href="https://agentmods.dev/skills/outlinedriven/odin-claude-plugin/resolve"><img src="https://agentmods.dev/badge/skills/outlinedriven/odin-claude-plugin/resolve.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 44 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,135 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00044 $0.03135
Opus 5.5 $0.00018 $0.01254
Sonnet 5.5 $0.00009 $0.00627
Haiku 4.5 $0.00004 $0.00314

Measured 27d ago against content hash 7ae38b4fc223, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

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 27d 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.

plugins/odin-git/skills/resolve/SKILL.md · 85 lines

How it starts

The opening of the file, as written. The whole thing — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Resolve review feedback

Contract

Field Bound contract
Trigger Addressing review feedback in local analyze or reception mode, or handling GitHub PR review comments and threads in autonomous, interactive, or summary mode.
Authority Reversible local plus human-gated GitHub actions. Local analyze and GitHub summary are read-only. Local reception writes only local source, test, and pushback-draft files. GitHub autonomous commits and pushes validated fixes and posts replies or resolves threads only after explicit human invocation; GitHub interactive applies approved local fixes and posts or resolves only after approval. Rollback is version control or undo locally, or reverting pushed commits, deleting replies, and unresolving threads remotely.
Side effect analyze: classifications and proposed solutions in chat. reception: local edits, tests, and a pushback draft. summary: a severity-grouped chat report. autonomous: validated commits and pushes, replies, and thread resolutions. interactive: approved local edits and approved replies or resolutions; no commit or push without an explicit request.
Done Every item is classified. analyze: each item has evidence and every valid issue has a recommended solution. reception: each item is clarified, implemented locally with its own test, or answered by drafted pushback. summary: every fetched item is grouped by severity with an ordered action list. autonomous: every unresolved item is evaluated, valid fixes land, handled threads are replied to and resolved, and only needs-human threads remain. interactive: every item has a recorded decision and every posted reply or resolved thread is approved.

Inputs

  • Mode: analyze or reception for local feedback; autonomous, interactive, or summary for GitHub PR feedback. Required. Use analyze when the user asks only whether comments are valid; GitHub autonomous is the default only after explicit invocation.
  • Feedback: raw review comments, a PR thread, or an inline suggestion for local modes. Required.
  • Code under review: the relevant source files or their location. Required for local modes and for any GitHub item that needs a verdict or fix.
  • GitHub target: blank for the current branch's PR, a PR number, or a comment/thread URL for a targeted autonomous run. interactive and summary accept a blank target or PR number.
  • GitHub access: an authenticated gh CLI with permission to enumerate review threads, top-level comments, and review bodies, map comment IDs to thread IDs, and post replies or resolve threads. Repository-provided helpers or equivalent paginated gh API/GraphQL calls may provide these operations.
  • Optional: a checkout of the PR branch for autonomous or interactive fixes, the current user's GitHub identity for interactive, and project test or check commands.

Read the full file on GitHub · 85 lines

Files

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.

Changes

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.

  1. 27d ago Changed · +6 lines 7ae38b4fc223
  2. 1mo ago Changed · +17 lines · +5 tokens per session 06112fb19f62
  3. 1mo ago First seen · 62 lines · 39 tokens per session scan A 23fb6bca08a4

Subscribe to this mod's changes

resolve is a skill published in the GitHub repository OutlineDriven/odin-claude-plugin (38 stars, last pushed 24d ago), licensed Apache-2.0. It adds 44 tokens to every session and 3,135 once invoked, about $0.0002 per session on Opus 5.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-06.

Related

Other skills, from other repositories

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens