by internet-court · Claude Skill · ★ 4.2k
Last updated: · Indexed by AgentSkillsHub · Auto-synced every 8h
🔒 Is internet-court-skill safe to install? View the security audit →
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 (), 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.
/plugin marketplace add internet-court/internet-court-skill
git clone https://github.com/internet-court/internet-court-skill ~/.claude/skills/internet-courtTaken from the project's README on GitHub. Check the security audit before running it.
No red flags found in any of the 11 categories — no credential harvesting, no data exfiltration, no curl-pipe-shell installer. Scanned against the SlowMist agent-security taxonomy, refreshed every 8 hours. Full audit →
| Stars | 4,157 |
| Forks | 87 |
| Language | TypeScript |
| Category | Claude Skill |
| Quality Score | 62.2507393580245/100 |
| Open Issues | 18 |
| Last Updated | 2026-08-19 |
| Created | 2026-06-16 |
| Platforms | browser, claude-code, codex, node |
| Est. Tokens | ~17k |
These tools work well together with internet-court-skill for enhanced workflows:
Looking for a internet-court-skill alternative? If you're comparing internet-court-skill with other claude skill tools, these 6 projects are the closest alternatives on Agent Skills Hub — ranked by topic overlap, star count, and community traction.
📚 Sync skills, agents, MCP, plugins to all AI CLI tools with one command and simplify team sharing.
Open-source cross-agent memory layer for coding agents via MCP. Compatible with Claude Code, Codex, Cursor, Wi
Superset is an agentic IDE to orchestrate 100+ coding agents in parallel. Run any agent with your own subscrip
Turn approved specs into long-running autonomous implementation. A minimal, adaptable SDD harness with Agent S
Agent Orchestration Command Center
Manage multiple Claude Code, OpenCode agents from either TUI or Web for easy access on mobile. Also supports M
Explore other popular claude skill tools:
internet-court-skill is The trust layer for agent-to-agent commerce — natural-language mandates, ERC-7710 delegated permissions, x402 payments, escrow, and dispute resolution as one open, catch-all Agent Skill / Claude Code . It is categorized as a Claude Skill with 4.2k GitHub stars.
internet-court-skill is primarily written in TypeScript. It covers topics such as a2a, adjudication, agent-payments.
The README on GitHub (github.com/internet-court/internet-court-skill) gives: /plugin marketplace add internet-court/internet-court-skill , then git clone https://github.com/internet-court/internet-court-skill ~/.claude/skills/internet-court. Usage details are in the same README.
The top alternatives to internet-court-skill on Agent Skills Hub include skillshare, memorix, superset. Each offers a different approach to the same problem space — compare them side-by-side by stars, quality score, and community activity.
Grades come from a rule-based scan built on the SlowMist agent-security taxonomy, covering 11 red-flag categories including credential harvesting, data exfiltration, and curl | sh installers. It is a first-layer scan, not a manual audit — we say so rather than overstate it.
The scale of the problem is documented independently: Liu et al. (2026), in a study of 31,132 agent skills, report that 26.1% contain security vulnerabilities. Our own full-catalog census is published as a citable open dataset.
Sources & who's responsible: