resolve

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

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

Written for no agent in particular: nothing here depends on one.

Good fit Use it to investigate review comments in a codebase, verify their validity, and compare at least three architectural approaches for each confirmed issue.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/outlinedriven/odin-codex-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-codex-plugin --skill resolve
Clone the repo
git clone --depth 1 https://github.com/OutlineDriven/odin-codex-plugin

Made for: Claude Code, Codex.

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-codex-plugin/resolve/github.svg)](https://agentmods.dev/skills/outlinedriven/odin-codex-plugin/resolve)
Your own site
<a href="https://agentmods.dev/skills/outlinedriven/odin-codex-plugin/resolve"><img src="https://agentmods.dev/badge/skills/outlinedriven/odin-codex-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-codex-plugin/resolve"><img src="https://agentmods.dev/badge/skills/outlinedriven/odin-codex-plugin/resolve.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
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. A grade says what 26 rules found in the file — not that it is safe.
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.00034 $0.00534
Opus 5.5 $0.00014 $0.00214
Sonnet 5.5 $0.00007 $0.00107
Haiku 4.5 $0.00003 $0.00053

Measured 1mo ago against content hash 6dccef0f8f73, 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 1mo 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. 1mo 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 (14 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 34 tokens to every session and 534 once invoked, about $0.0001 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-08-30.

Related

Other skills, from other repositories

improve-codebase-architecture

Surface deepening refactors that turn shallow modules into deep ones, informed by CONTEXT.md and docs/adr/. Use when the user asks to improve architecture, find refactor candidates, raise testability, or make a codebase more agent-navigable. Skip for single localized fixes.

OutlineDriven/odin-gemini-cli-extension · 69 tokens

security-review

Adversarial security audit — STRIDE, OWASP Top 10, supply-chain (CVE/SBOM), secrets scan, auth/authz analysis. Use on changes touching auth, input parsing, deserialization, network I/O, dependencies, or secrets; before any production release or external-surface PR.

OutlineDriven/odin-gemini-cli-extension · 66 tokens

pr-reviews

Review code changes on a given GitHub PR using gh CLI. Use when the user asks to review a pull request, analyze PR diffs, or provide feedback on open PRs with structured quality, security, and testing assessments.

OutlineDriven/odin-gemini-cli-extension · 50 tokens

resolve

Resolve code review comments by verifying validity, then proposing multiple architectural solutions (not naive fixes) for confirmed issues. Use when addressing review feedback or analyzing comment validity.

OutlineDriven/odin-gemini-cli-extension · 34 tokens

reviews

Review the code changes on the current branch. Use when the user asks to review their current work, analyze recent commits, or get a code quality assessment of the active branch against the main branch.

OutlineDriven/odin-gemini-cli-extension · 41 tokens

gh-address-comments

Help address review/issue comments on the open GitHub PR for the current branch using gh CLI; verify gh auth first and prompt the user to authenticate if not logged in.

OutlineDriven/odin-gemini-cli-extension · 39 tokens