agentmods.dev

conflict-resolution

conflict-resolution is a skill for Claude Code from mu4farooqi/superwiser. It costs 30 tokens per session (393 once invoked), scanned A, original, MIT.

A procedure for handling contradictory user preferences found by Superwiser, such as different indentation rules given at different times. It tells the agent to show the conflict and wait for the user’s choice.

In plain words
What is it for?
Use it when Superwiser reports a conflict while searching rules, listing rules, or loading preferences.
Why use it?
It prevents the agent from silently guessing which conflicting preference should apply.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the superwiser plugin — 2 skills, 12 commands, 4 hooks, 1 MCP server shipped together

not rated 6repo 7mo ago A scan 30 tokens original MIT

Good fit Use it when Superwiser reports a conflict while searching rules, listing rules, or loading preferences.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/mu4farooqi/superwiser/conflict-resolution
View source ↗ mu4farooqi/superwiser
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 mu4farooqi/superwiser --skill conflict-resolution
Clone the repo
git clone --depth 1 https://github.com/mu4farooqi/superwiser

Made for: Claude Code.

Or install superwiser, the plugin that ships this one along with the rest of its 2 skills, 12 commands, 4 hooks, 1 MCP server.

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 conflict-resolution

README.md
[![agentmods](https://agentmods.dev/badge/skills/mu4farooqi/superwiser/conflict-resolution/github.svg)](https://agentmods.dev/skills/mu4farooqi/superwiser/conflict-resolution)
Your own site
<a href="https://agentmods.dev/skills/mu4farooqi/superwiser/conflict-resolution"><img src="https://agentmods.dev/badge/skills/mu4farooqi/superwiser/conflict-resolution/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 conflict-resolution

Your own site · 80×15
<a href="https://agentmods.dev/skills/mu4farooqi/superwiser/conflict-resolution"><img src="https://agentmods.dev/badge/skills/mu4farooqi/superwiser/conflict-resolution.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 30 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 393 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.00030 $0.00393
Opus 5 $0.00015 $0.00197
Sonnet 5 $0.00006 $0.00079
Haiku 4.5 $0.00003 $0.00039

Measured 9d ago against content hash 49833e72a538, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

conflict-resolution 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 9d 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/superwiser/skills/conflict-resolution/SKILL.md · 45 lines

What it actually says

Conflict Resolution

When any Superwiser tool returns results containing "⚠️ CONFLICT [id]", you must resolve the conflict before proceeding.

What Is a Conflict?

A conflict occurs when the user has expressed contradictory preferences at different times. For example:

  • "Always use tabs for indentation" vs "Use 2-space indentation"
  • "Prefer functional components" vs "Use class components for state"

How to Resolve

  1. Present the conflict clearly to the user:

    SuperWiser Conflict [abc123]:
I found conflicting preferences:
1. "Always use tabs for indentation" (from when you were setting up the project)
2. "Use 2-space indentation" (from your React work last week)

Which should I follow? Or do they apply in different contexts?

  2. Wait for the user's response. They can:

    • Pick a number (e.g., "1" or "use the first one")
    • Say "both" or "all" if both rules should be kept
    • Explain when each applies (e.g., "tabs for Python, spaces for JS")
    • Say "skip" to ignore for now

  3. After the user responds, continue with your work. You do NOT need to:

    • Call any tools to resolve or delete rules
    • Process the response in any special way
    • The conflict resolution is handled automatically in the background

Important

  • Do NOT skip conflicts - they indicate important ambiguity in user preferences
  • Do NOT guess which rule to follow - always ask the user
  • Do NOT call any MCP tools to "resolve" the conflict - just continue after they respond
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. 9d ago First seen · 45 lines · 30 tokens per session scan A 49833e72a538

Subscribe to this mod's changes

conflict-resolution is a skill published in the GitHub repository mu4farooqi/superwiser (6 stars, last pushed 7mo ago), licensed MIT. It adds 30 tokens to every session and 393 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-31.

Related

Other skills, from other repositories

systematic-debugging

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

obra/superpowers · 21 tokens

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

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

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

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens

next-partial-prefetching-adoption

Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…

vercel/next.js · 103 tokens