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 manishiitg/coding-agent-loop --skill dispute-to-reconciled-outcomegit clone --depth 1 https://github.com/manishiitg/coding-agent-loopWrote 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/manishiitg/coding-agent-loop/dispute-to-reconciled-outcome)<a href="https://agentmods.dev/skills/manishiitg/coding-agent-loop/dispute-to-reconciled-outcome"><img src="https://agentmods.dev/badge/skills/manishiitg/coding-agent-loop/dispute-to-reconciled-outcome/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/manishiitg/coding-agent-loop/dispute-to-reconciled-outcome"><img src="https://agentmods.dev/badge/skills/manishiitg/coding-agent-loop/dispute-to-reconciled-outcome.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.00025 | $0.00750 |
| Opus 5.5 | $0.00010 | $0.00300 |
| Sonnet 5.5 | $0.00005 | $0.00150 |
| Haiku 4.5 | $0.00003 | $0.00075 |
Grade A, and why
dispute-to-reconciled-outcome 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 20d 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 — 48 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Dispute to Reconciled Outcome
Outcome
Track one dispute through evidence review, approved submission, provider outcome and finance reconciliation. These are distinct states.
When to use
Use for an authorized dispute with a known account, payment, deadline, owner and finance source. Start with one manual case.
Discovery and user direction
Inspect Finance Crews and Dispute Review, current case, payment, prior submissions, relevant sources, owner policy and ledger. Propose Crew reuse or creation and show the route before Builder applies it. Selection leaves setup pending.
Required inputs
Bind legal entity, provider account and mode, dispute, payment, customer, amount and currency, case revision, reason, response deadline with timezone, source IDs, evidence privacy rule, submission approver and finance owner. Identify the authoritative source for the provider outcome and principal and fee ledger entries.
Plan and AgentWorks tools
Use Billing Operations Coordinator with Dispute Review to emit dispute-case/v1. Set the Crew step's JSON context_output and a structural validation_schema. Run the bundled business validator as a blocking step before Revenue & Close Analyst consumes the exact artifact. Finance emits dispute-finance-review/v1; validate that pair. Stage evidence and request an owner decision before a separate approved submission route. A current processor receipt, not the draft or approval, proves submission.
Knowledge and persistence
Save the provider case revision, payment and account IDs, source references, evidence packet hash, decision, submission idempotency key, provider receipt, outcome revision, ledger IDs and next review time. Re-read case status and deadline before every submission attempt or follow-up; deduplicate against earlier provider submissions.
Validation and reporting
The validator checks scope, evidence and deadline presence, submission and outcome receipts, finance status and ledger joins. Fictional pending case and pending finance review, submitted case and awaiting finance, and closed loss with ledger review pass. Invented submission and a premature finance win fail. The reporting dashboard separates evidence needed, awaiting approval, submitted, under review, provider decided, and finance reconciled, with source links and costs.
What ships with it
13 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- examples/dispute-case-closed-lost.json 1.5 KB
- examples/dispute-case-pending.json 1.0 KB
- examples/dispute-case-submitted.json 1.3 KB
- examples/dispute-finance-awaiting.json 715 B
- examples/dispute-finance-pending.json 714 B
- examples/dispute-finance-reconciled.json 981 B
- examples/invalid-dispute-case.json 1.0 KB
- examples/invalid-dispute-finance-won.json 708 B
- playbook.json 5.0 KB
- references/team-and-handoffs.md 3.5 KB
- scripts/test_validate_handoff.py 2.7 KB runs code
- scripts/validate_handoff.py 8.7 KB runs code
- SETUP.json 3.3 KB
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.
- 20d ago First seen · 48 lines · 25 tokens per session scan A f479ea59e109
dispute-to-reconciled-outcome is a skill published in the GitHub repository manishiitg/coding-agent-loop (13 stars, last pushed 19d ago), licensed MIT. It adds 25 tokens to every session and 750 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-09-27.
Other skills, from other repositories
gridcraft
Headless spreadsheets with GridCraft (XLSX/CSV/TSV workbooks, formula evaluation, recalculation, PDF export), provisioned on demand by pi-craft. Use for "build a budget spreadsheet with formulas", "convert this xlsx to csv", "what does this formula evaluate to", "change a cell and recalculate the totals", "export the…
goga-cell-go
Golang rules for implementing CODEMANIFEST contracts.
loan-officer-assistant
Skill "loan-officer-assistant" from aimerdoux/wavex-os, covering 🏦 loan officer assistant agent, 🧠 your identity & memory, 🎯 your core mission, 🚨 critical rules you must follow and 📋 your technical deliverables.
finance-tracker
Skill "finance-tracker" from aimerdoux/wavex-os, covering finance tracker agent personality, 🧠 your identity & memory, 🎯 your core mission, maintain financial health and performance and enable strategic financial decision making.
bookkeeper
Skill "bookkeeper" from aimerdoux/wavex-os, covering 📒 bookkeeper & controller agent, 🧠 your identity & memory, 🎯 your core mission, 🚨 critical rules you must follow and 📋 your technical deliverables.
financial-analyst
Skill "financial-analyst" from aimerdoux/wavex-os, covering 📊 financial analyst agent, 🧠 your identity & memory, 🎯 your core mission, 🚨 critical rules you must follow and 📋 your technical deliverables.