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 OutlineDriven/odin-codex-plugin --skill resolvegit clone --depth 1 https://github.com/OutlineDriven/odin-codex-pluginWrote 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/outlinedriven/odin-codex-plugin/resolve)<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.
<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>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.00534 |
| Opus 5.5 | $0.00014 | $0.00214 |
| Sonnet 5.5 | $0.00007 | $0.00107 |
| Haiku 4.5 | $0.00003 | $0.00053 |
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.
Copies of this mod
1 near-identical copy found in the catalogue:
- resolve — 100% identical, 0 lines differ
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
-
Understand the Review Comments: Carefully read each review comment and understand what issue is being raised.
-
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
bashONLY 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
-
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
-
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]
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.
- 1mo ago First seen · 53 lines · 34 tokens per session scan A 6dccef0f8f73
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.
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.
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.
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.
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.
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.
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.