internet-court/internet-court-skill

Internet Court Skill

An open skill for agent-to-agent contracts.

Agents are beginning to transact, negotiate, and pay one another without humans in the loop. What they still lack is a way to trust each other. The building blocks already exist, but they are fragmented, and each one is built for the happy path. When a deal goes wrong, every layer passes the problem down the line.

Internet Court does two things. It connects that fragmented ecosystem into a single open skill, and it builds in adjudication: when two agents make a deal, they also agree up front how it will be settled if something goes wrong, written into the contract itself. Payments let agents transact. Adjudication makes them accountable — and accountability is what turns transactions into a real economy.

This repository is that skill: a master router (SKILL.md), the Internet Court connector skills, and vendored copies of the official skills published by the protocols in the stack. It gives an agent everything it needs to structure a deal, hold funds safely, and settle disagreements fairly — all in natural language, at internet speed.

The stack

From discovery to disputes, agentic commerce runs through six layers. Each existing standard solves one of them and assumes everything goes right. Internet Court is the open skill that connects them and adds the layer nobody else owns — verification and dispute resolution — so the whole lifecycle of a deal sits behind one skill instead of a stack the agent has to wire up itself.

The verification & disputes layer is the one Internet Court exists to add. Agents agree in advance who judges a dispute if one arises — GenLayer, Kleros, UMA, or whatever they choose. Most deals never get there: when both sides agree, the contract simply settles. What the skill standardizes is how the contract is structured around that choice, for the cases that fall off the happy path.

The consortium

Internet Court is built by a consortium of companies working across the agentic commerce stack — not a closed product from a single vendor. The founding members span every layer, and each member's protocol is embedded directly into the standard.

Founding members: GenLayer, MetaMask, OKX, NEAR, Starknet, x402, 0G Labs, ZKsync, Nansen, Kleros, Privy, AntSeed, Collective Memory, UMA, Arkhai, AltLayer, Anoma, AppLayer, BNB Chain, LI.FI, Chainbase, io.net, Heurist, Chutes, ChainGPT, OpenServ, Humanode, Humanity Protocol.

The standard is open and openly governed — any agent can adopt it now. Not every founding member ships a public agent skill yet; the vendored table below is the set available in this repository today, and it grows as members publish.

Repository layout

SKILL.md                            Master skill — start here; routes to everything below
integrations/                       Internet Court connector & adapter skills
vendored/                           Committed copies of official protocol skills (69 skills, 23 owners)
skills-lock.json                    Pinned source + hash + refresh command per vendored skill

Two kinds of content:

• First-party — only the master skill and the connectors. This repo never re-implements a protocol's own skill.
• Vendored — copies of publicly published skills, fetched from official sources and pinned in skills-lock.json.

Vendored skills

Pinned hashes and refresh commands per skill: skills-lock.json and vendored/README.md.

Install

Internet Court is one catch-all skill. Whatever harness you use, only the root SKILL.md is registered and triggered; it routes to the vendored protocol and connector skills and pulls them into context on demand — from disk when the whole repo is installed, otherwise fetched from https://raw.githubusercontent.com/internet-court/internet-court-skill/main/<path>. Installing the whole repository (not just SKILL.md) bundles every sub-skill for offline use, but a root-only install still works via that fallback.

Pick your harness:

Claude Code (plugin — recommended)

# in a Claude Code session:
/plugin marketplace add internet-court/internet-court-skill
/plugin install internet-court@internet-court
# update later:  /plugin marketplace update internet-court

Or load it locally without the marketplace — claude --plugin-dir <path-to-clone> — or just clone it as a plain skill:

git clone https://github.com/internet-court/internet-court-skill ~/.claude/skills/internet-court

npx skills (skills.sh)

npx skills add internet-court/internet-court-skill   # installs the root skill
# update later:  npx skills update

Codex

git clone https://github.com/internet-court/internet-court-skill ~/.agents/skills/internet-court
# or, per-repo:  .agents/skills/internet-court   ·   or:  npx skills add internet-court/internet-court-skill

Codex scans recursively, so it will also surface the bundled sub-skills as separate skills; the root skill is the intended entry point.

opencode

git clone https://github.com/internet-court/internet-court-skill ~/.config/opencode/skills/internet-court

opencode also reads ~/.claude/skills/ and ~/.agents/skills/, so a single clone into any of those is enough.

OpenClaw

openclaw skills install git:internet-court/internet-court-skill
# update later:  openclaw skills update

OpenClaw installs the root skill; sub-skills are fetched on demand via the raw-URL fallback above.

Hermes

git clone https://github.com/internet-court/internet-court-skill ~/.hermes/skills/internet-court
# or as a tap:  hermes skills tap add internet-court/internet-court-skill

Prefer the clone/tap over hermes skills install <url>, which currently fetches only SKILL.md and misses bundled reference files.

After installing, give the agent a task — the master skill routes to the sub-skills — or say "Install the Internet Court skill" for the guided introduction. The Claude Code marketplace and the plugin live in the same repository, which is why both /plugin marketplace add and /plugin install reference internet-court.

Some vendored skills need their provider's credentials to act (e.g. OKX API keys, ChainGPT API key, Chainbase API key); each skill documents its own requirements.

License

The first-party work in this repository — the master skill and the connectors — is released under the MIT License. Vendored skills under vendored/ are copies of upstream projects and remain under their own licenses; see each skill's source repository (and skills-lock.json) for terms.

© 2026 Internet Court Consortium · Open standard, openly governed · internetcourt.org