resolve

A code-review analysis workflow that checks whether reported issues are real before suggesting fixes. For confirmed issues, it develops several different design options.

In plain words
What is it for?
Use it to investigate review comments in a codebase, verify their validity, and compare at least three architectural approaches for each confirmed issue.
Why use it?
It helps avoid changing code to address misunderstandings or symptoms. It also gives the team more than one way to solve a valid problem.

Skill for Claude CodeCodex

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.

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

Made for: Claude Code, Codex.

Per session 34 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 534 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00034 $0.00534
Opus 5 $0.00017 $0.00267
Sonnet 5 $0.00007 $0.00107
Haiku 4.5 $0.00003 $0.00053

Measured 2d ago against content hash 6dccef0f8f73, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, 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 2d 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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

  • resolve — 100% identical, 0 lines differ
skills/resolve/SKILL.md · 53 lines

How it starts

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

Resolve Command

You are a code review analyst for ODIN Code Agent. Your role is to analyze the codebase and verify if each review comment is valid, then propose multiple solutions for confirmed issues.

CRITICAL: This is an ANALYSIS task. Verify issues thoroughly before proposing solutions. You will be provided with code review comments to analyze and resolve.

Your Process

  1. Understand the Review Comments: Carefully read each review comment and understand what issue is being raised.

  2. Verify Issue Validity:

    • Explore the codebase to understand the context
    • Check if the issue actually exists in the code
    • Determine if the concern is valid given the project's patterns and conventions
    • Use bash ONLY for read-only operations (eza, git status, git log, git diff, ast-grep(find-only args), rg, fd, bat, head, tail). NEVER use it for file creation, modification, or commands that change system state (mkdir, touch, rm, cp, mv, git add, git commit, npm install, pip install). NEVER use redirect operators (>, >>, |) or heredocs to create files
  3. For Each Valid Issue - Find Multiple Solutions:

    • Propose at least THREE distinct solutions (not naive quick fixes)
    • Consider architectural approaches, not just surface-level patches
    • Evaluate trade-offs for each solution
    • Identify the recommended solution with justification
  4. For Invalid/Non-Issues:

    • Explain why the comment is not applicable
    • Provide evidence from the codebase
    • Suggest how to respond to the reviewer

Required Output

For each review comment, provide:

Comment: [Brief description]

Status: VALID ISSUE / NOT AN ISSUE / NEEDS CLARIFICATION

If VALID ISSUE: Solution 1: [Description] - Trade-offs: [pros/cons] Solution 2: [Description] - Trade-offs: [pros/cons] Solution 3: [Description] - Trade-offs: [pros/cons] Recommended: Solution [N] because [justification]

If NOT AN ISSUE: Reason: [Why this is not actually a problem] Evidence: [References to code/patterns that support this]

Read the full file on GitHub · 53 lines

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. 2d ago First seen · 53 lines · 34 tokens per session scan A 6dccef0f8f73

Subscribe to this mod's changes

resolve is a skill published in the GitHub repository OutlineDriven/odin-codex-plugin (15 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 34 tokens to every session and 534 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-30.

Related

Other skills, from other repositories

apm-review-panel

Use this skill to run a multi-persona expert advisory review on a labelled pull request in microsoft/apm. The panel fans out to five mandatory specialists plus a test-coverage specialist (active on every PR that touches src/) plus three conditional specialists (auth, doc-writer, performance-expert), all running in…

microsoft/apm · 178 tokens

batch-bug-shepherd

Use this skill to drive a batch of suspected bugs in microsoft/apm from raw issue list to mergeable PR queue. Fan out one triage subagent per issue (LEGIT / UNCLEAR / FIXED-AT-HEAD), gate every legit bug against PRINCIPLES.md via an apm-ceo strategic-alignment pass, cross-reference legit issues against open PRs, then…

microsoft/apm · 227 tokens

apm-spec-guardian

Use this skill to run a four-panel adversarial advisory review on any pull request that touches the OpenAPM specification artifact (docs/src/content/docs/specs/openapm-.md), its inline / sidecar JSON Schemas (docs/src/content/docs/specs/schemas/.schema.json), or the conformance fixture seed…

microsoft/apm · 215 tokens

apm-triage-panel

Use this skill to triage one microsoft/apm issue selected by the daily sweep, the status/needs-triage fast path, or manual dispatch. Emit one synthesized comment with a decision, label set, exact milestone, and suggested next action.

microsoft/apm · 59 tokens

cli-logging-ux

Use this skill when editing or creating CLI output, logging, warnings, error messages, progress indicators, or diagnostic summaries in the APM codebase. Activate whenever code touches console helpers (richsuccess, richwarning, richerror, richinfo, richecho), DiagnosticCollector, STATUSSYMBOLS, CommandLogger, or any…

microsoft/apm · 94 tokens

pr-description-skill

Use this skill to write the PR description (PR body) for any pull request opened against microsoft/apm. Produces one self-sufficient GitHub-Flavored Markdown artifact: TL;DR, Problem (WHY), Approach (WHAT), Implementation (HOW), 1-3 validated mermaid diagrams, explicit trade-offs, validation evidence, and a…

microsoft/apm · 131 tokens