dispute-respond SKILL.md skillA
dispute-respond from runxhq/runx is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add runxhq/runx/dispute-respond@git:20261023.420f372Pins git:20261023.420f372 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- runxhq/runx
- Path
skills/dispute-respond/SKILL.md- Versions recorded
- 8
- Latest version
- git:20261023.420f372, committed Oct 23, 2026
- First version recorded
- May 20, 2026
- Size
- 5,566 bytes
- Repository stars
- 104
- License
- Apache-2.0
Prepare and explicitly file an evidence-bound payment dispute response using native receipt proof, approval, provider execution, and independent readback.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Dispute Respond Turn one provider dispute event and the exact Runx payment history behind it into a reviewable response posture. A good dispute packet does not merely tell a persuasive story: it proves which charge and refund receipts were consulted, which external evidence may be cited, what remains unknown, and why the operator should accept, contest, review, or acknowledge an existing refund. The default `file-response` runner prepares the evidence-bound response, files it through the selected configured provider after one exact approval, and requires independent readback. `respond` remains the explicit draft-only runner, while `file` consumes an admitted prior response packet without repeating the evidence work. No runner closes a dispute, moves money, or invents provider acceptance. ## When to use it Use `dispute-respond` after a provider has created a bounded dispute event and the original charge should exist in Runx receipt history. Use `refund` when the operator chooses a new reversal rather than a dispute response. If the original settlement cannot be proven, gather that evidence before contesting. ## How it works …
Read the whole file at its exact version.
How to install
mdr add runxhq/runx/dispute-respond@sha256:cde9896386d6a726The line at the top of this page pins the label git:20261023.420f372, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_r2rach2sexrparob)
5 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 8 versions of this file, between May 20, 2026 and Oct 23, 2026, about one every 22 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261023.420f372 latest | 2026-10-23 | 420f372 | 5,566 B | A | view · diff |
| git:20261011.e2a7e0c | 2026-10-11 | e2a7e0c | 5,546 B | A | view · diff |
| git:20261008.1a28e75 | 2026-10-08 | 1a28e75 | 5,451 B | A | view · diff |
| git:20260808.8b7af2a | 2026-08-08 | 8b7af2a | 5,478 B | A | view · diff |
| git:20260723.6e5370b | 2026-07-23 | 6e5370b | 5,426 B | A | view · diff |
| git:20260609.7560e07 | 2026-06-09 | 7560e07 | 5,976 B | A | view · diff |
| git:20260521.02561b0 | 2026-05-21 | 02561b0 | 1,415 B | A | view · diff |
| git:20260520.cb93ef7 | 2026-05-20 | cb93ef7 | 1,388 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (5566 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
runxhq/runx · 104 stars · license Apache-2.0 · pushed 2026-11-05 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_r2rach2sexrparob GET https://markdownregistry.com/api/v1/resolve?ref=runxhq/runx/dispute-respond GET https://markdownregistry.com/api/v1/blob/cde9896386d6a726c5a53c3bafbb722e9c03f688a5bb9c15b15e1f2ce066adb5
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.