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 po4yka/llm-wiki-skills --skill llm-wiki-conflict-resolvergit clone --depth 1 https://github.com/po4yka/llm-wiki-skillsWrote 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/po4yka/llm-wiki-skills/llm-wiki-conflict-resolver)<a href="https://agentmods.dev/skills/po4yka/llm-wiki-skills/llm-wiki-conflict-resolver"><img src="https://agentmods.dev/badge/skills/po4yka/llm-wiki-skills/llm-wiki-conflict-resolver/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/po4yka/llm-wiki-skills/llm-wiki-conflict-resolver"><img src="https://agentmods.dev/badge/skills/po4yka/llm-wiki-skills/llm-wiki-conflict-resolver.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.00061 | $0.00658 |
| Opus 5.5 | $0.00024 | $0.00263 |
| Sonnet 5.5 | $0.00012 | $0.00132 |
| Haiku 4.5 | $0.00006 | $0.00066 |
Grade A, and why
llm-wiki-conflict-resolver 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.
How it starts
The opening of the file, as written. The whole thing — 104 lines — stays where its author put it; the contents beside it link to each section on GitHub.
LLM-Wiki Conflict Resolver
Goal
Turn contradictions into explicit review decisions without silently rewriting truth.
When to use
wiki-lintreports two or more pages making contradictory claims about the same fact.- A provenance check finds a claim whose cited source no longer supports it.
- A human reviewer flags disagreement between a decision note and a concept page.
- Two pages define the same term differently (terminology drift) or appear to duplicate the same concept.
- A claim looks stale (tool status, recommendation, or decision that may have changed) and needs a review decision rather than a silent edit.
Inputs
- Conflicting pages or lint report.
- Supporting source pages and raw sources.
- Desired mode: analyze, propose resolution, or apply approved patch.
Procedure
1. Define conflict set
Group conflicting claims by topic. For each claim, record:
- page path;
- claim text;
- status;
- source support;
- update date;
- confidence/review state;
- whether it is extracted, inferred, ambiguous or synthesis.
2. Classify conflict type
Use:
| Type | Meaning |
|---|---|
| stale | One claim was true but is now outdated. |
| scope mismatch | Claims are true under different conditions. |
| source disagreement | Sources genuinely disagree. |
| inference error | A page inferred too much. |
| terminology drift | Same term used differently. |
| duplicate concept | Two pages should be merged or separated. |
3. Present evidence
Show concise evidence and provenance for each side. Do not use generated summaries as the only evidence for high-impact conflicts.
4. Propose resolution options
Possible actions:
- mark one page stale;
- split by scope;
- add caveat;
- demote claim to ambiguous;
- merge duplicate pages;
- create a decision note;
- request external source verification.
5. Apply only approved changes
In apply mode, patch only the approved resolution and append to wiki/log.md.
Output
## Conflict summary
## Claims in conflict
## Evidence
## Conflict type
## Resolution options
## Recommended review decision
## Approved patches
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 · 104 lines · 61 tokens per session scan A 6b4f211ee5f7
llm-wiki-conflict-resolver is a skill published in the GitHub repository po4yka/llm-wiki-skills (4 stars, last pushed 2d ago), licensed MIT. It adds 61 tokens to every session and 658 once invoked, about $0.0002 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-31.
Other skills, from other repositories
obsidian-memory
Explicit-only Obsidian memory workflow. Use when the user explicitly asks to work with an Obsidian vault, LLM wiki, agent memory, RAW/source ingest, provenance, QUERY, LINT, or release safety for a markdown knowledge system. Do not auto-route ordinary coding sessions into external vault workflows.
wiki-lint
Health-check a wiki vault. Finds orphan pages (no inbound links), dead wikilinks (point to non-existent pages), missing frontmatter fields, stale claims, empty sections, and pages absent from catalog.md. Produces a structured report with severity tiers and proposes concrete fixes — but does not auto-apply them unless…
save
File the current Claude conversation (or a specific insight from it) as a structured wiki note. Auto-detects the right type (decision, answer, session-log, technique, ADR), writes appropriate frontmatter, places the file in the correct wiki folder, and updates catalog.md, journal.md, hot.md. Use when the user says…
librarian
Orchestrate vault knowledge workflows using the Librarian MCP server. Ingest solutions, search prior art, explore the knowledge graph, log daily learnings.
wiki-export
Export a vault's wiki either as a single portable file (llms.txt or llms-full.txt per the llmstxt.org standard) or as an OKF knowledge bundle (Google's Open Knowledge Format v0.1 — a shareable directory of markdown files any AI agent can consume). Use when the user says "export my wiki", "make an llms.txt", "share my…
wiki-query
Answer a question using ONLY the existing wiki vault as the knowledge base — no web search, no general LLM knowledge. Reads hot.md first (cheap recent context), then catalog.md to navigate, then drills into specific pages, then optionally semantic-searches the wiki, and synthesizes an answer with citations. Use when…