agentmods.dev

resolve

A conflict-review command for Grainulator, a research system that records claims and their supporting evidence.

In plain words
What is it for?
Use it to inspect conflicting claims, compare their evidence and context, choose or research a resolution, and update the compiled sprint state.
Why use it?
It handles cases where the system finds claims that disagree and cannot decide which one should remain active.

Skill for Claude CodeCodex

87 4mo ago A scan 13 tokens original MIT
View the source file grainulation/grainulator
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/grainulation/grainulator/resolve
Any agent
npx skills add grainulation/grainulator --skill resolve
Clone the repo
git clone --depth 1 https://github.com/grainulation/grainulator

Made for: Claude Code, Codex.

Per session 13 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 414 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.00013 $0.00414
Opus 5 $0.00006 $0.00207
Sonnet 5 $0.00003 $0.00083
Haiku 4.5 $0.00001 $0.00041

Measured yesterday against content hash e64db8305d56, 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 yesterday.

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.

skills/resolve/SKILL.md · 53 lines

What it actually says

/resolve -- Adjudicate a conflict

The user wants to resolve a conflict between claims that the compiler couldn't auto-resolve.

Arguments

$ARGUMENTS

Expected format: /resolve (show all conflicts) or /resolve <claim_id> <claim_id> (resolve specific pair)

Instructions

  1. Get current conflicts via wheat_compile or wheat_status. List all unresolved conflicts.

  2. If no claim IDs provided, show all conflicts and ask which to resolve. If claim IDs provided, focus on that pair.

  3. Present both sides: Show both conflicting claims with full context — content, evidence tier, source origin, when added, and any corroborations.

  4. Resolve: Either:

    • Ask the user to decide (present the tradeoff clearly)
    • If the user asks you to investigate, do additional research and recommend

  5. Apply resolution via wheat_resolve:

    • Winner stays active
    • Loser becomes superseded with resolved_by set to winner's ID
    • Remove conflict references from conflicts_with

  6. Run wheat_compile to verify the conflict is resolved.

  7. Print result:

    Resolved: <winner_id> over <loser_id>
Reason: <why>
Remaining conflicts: <N>

Next steps:
  /resolve            -- resolve next conflict
  /brief              -- compile if all conflicts resolved
  /blind-spot         -- check for gaps after resolution
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. yesterday First seen · 53 lines · 13 tokens per session scan A e64db8305d56

Subscribe to this mod's changes

resolve is a skill published in the GitHub repository grainulation/grainulator (87 stars, last pushed 4mo ago), licensed MIT. It adds 13 tokens to every session and 414 once invoked, about $0.0001 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.

Code reviewFrontendProject managementclaudeclaude-aiclaude-codeclaude-code-plugincompilercompiler-frontend
Related

Other skills, from other repositories

project-sizing-guide

Software project effort estimation assistant. Outputs three-point estimates (optimistic/most-likely/pessimistic values with confidence intervals), T-shirt sizes, or Function Point Analysis (FPA) counts. Triggered when users ask 'how long will this feature take,' need to assess project workload, perform PERT…

zebbern/claude-code-guide · 86 tokens

sprint-wrap-up

End-of-sprint checklist — finalize results, clean up worktrees, update docs, prepare for retro. Any agent can run this.

loopdive/js2 · 32 tokens

session-wrapup

End-of-session checkpoint — append diary, update active sprint doc with interim results/retro, write tech-lead handoff, commit and push. Use before /compact or at end-of-day. Distinct from sprint-wrap-up which closes a sprint.

loopdive/js2 · 54 tokens

shutdown-dev

Cleanly shut down a dev teammate — instruct them to write a context summary to plan/agent-context/{name}.md first, receive their approval, verify process exit. Use for scale-down, rotation, sprint wrap-up.

loopdive/js2 · 48 tokens

sprint-planning

Collaborative sprint planning — validate issues, prioritize, get architect/SM input, create task queue. Any agent can facilitate.

loopdive/js2 · 30 tokens

sprint-retrospective

Run a sprint retrospective — gather data, analyze incidents, propose action items. Any agent can facilitate.

loopdive/js2 · 26 tokens