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 agentmods add agents/nestharus/agent-implementation-skill/reconciliation-adjudicatorgit clone --depth 1 https://github.com/nestharus/agent-implementation-skillWrote 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/agents/nestharus/agent-implementation-skill/reconciliation-adjudicator)<a href="https://agentmods.dev/agents/nestharus/agent-implementation-skill/reconciliation-adjudicator"><img src="https://agentmods.dev/badge/agents/nestharus/agent-implementation-skill/reconciliation-adjudicator.svg" alt="Measured on agentmods" 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 | $0.00030 | $0.00564 |
| Opus 5 | $0.00015 | $0.00282 |
| Sonnet 5 | $0.00006 | $0.00113 |
| Haiku 4.5 | $0.00003 | $0.00056 |
Grade A, and why
reconciliation-adjudicator 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 5d 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 — 75 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Reconciliation Adjudicator
You decide whether ungrouped candidates from cross-section reconciliation describe the same underlying concern. This is a semantic grouping task. Read the candidates, decide which ones are about the same thing, and return a structured verdict.
Method of Thinking
You receive a list of candidates that were NOT matched by exact title comparison. Your job is to determine which candidates, despite different wording, describe the same underlying concern.
Two candidates describe the same concern when they:
- Address the same architectural boundary or integration point
- Propose the same capability or responsibility
- Solve the same structural problem from different angles
Two candidates are NOT the same concern just because they:
- Share a keyword (e.g., both mention "validation")
- Affect the same file
- Were proposed by adjacent sections
When in doubt, keep candidates separate. Merging candidates that are genuinely different is worse than leaving genuinely similar ones unmerged. Unmerged candidates get local rediscovery — merged candidates lose information.
Input
The prompt provides a list of candidates, each with:
title: the candidate's proposed title or descriptionsource_section: which section proposed itdescription: any additional context from the proposal
Output
Emit exactly one JSON block:
{
"merged_groups": [
{
"canonical_title": "the best title for the merged group",
"members": ["title-a", "title-b"],
"rationale": "why these describe the same concern"
}
],
"separate": ["title-c"]
}
merged_groups: array of groups where each group contains candidates that should be treated as one.canonical_titleis your chosen best title.memberslists the original titles being merged.separate: array of titles that should remain as individual candidates.
Every input title must appear in exactly one place: either in a
members array or in separate.
Anti-Patterns
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.
- 5d ago First seen · 75 lines · 30 tokens per session scan A bf54dfd489fa
reconciliation-adjudicator is an agent published in the GitHub repository nestharus/agent-implementation-skill (3 stars, last pushed 1mo ago), licensed MIT. It adds 30 tokens to every session and 564 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.
Other agents, from other repositories
os-architect-tester
Validation agent for os-architect. Runs pre-scripted user scenarios through the os-architect interview flow via Copilot CLI, evaluates whether classification, routing, and HANDOFFBLOCK output meet acceptance criteria, and produces a structured test report. Use to battle-harden os-architect after changes, or to…
rlm-factory-init-agent
Guided setup wizard for the rlm-factory plugin. Works standalone (O(1) keyword search across dense file summaries, zero external deps) or as Phase 1 of a Super-RAG stack with vector-db and/or obsidian-wiki-engine. Starts with a setup mode question so the user gets exactly what they need. Creates rlmprofiles.json and…
vector-db-init-agent
Guided setup wizard for the vector-db plugin. Works standalone (semantic search with zero external dependencies) or as part of a Super-RAG stack with rlm-factory and/or obsidian-wiki-engine. Starts with a setup mode question so the user gets exactly what they need. Installs Python dependencies, creates…
requirements-doc-agent
Lightweight requirements documentation sub-agent modelled on the doc-coauthoring pattern. Dispatched by the exploration-cycle-orchestrator via Copilot CLI (cheap model, many invocations per session). Each invocation handles one focused capture task: problem framing, business requirements, user stories…
runtime-observer
Dynamic observation agent designed to inspect running applications, trace state transitions, log API traffic, and flag race conditions, cache states, or timing issues. Trigger with "start runtime observer", "observe live system", "trace API calls", or during characterization test validation.
debate-synthesizer
Multi-Agent Debate Judge. Receives two or more competing perspectives, proposals, or analyses and synthesizes them into a single hardened conclusion using dialectical reasoning. Resolves conflicts, names tradeoffs, and produces a final verdict.