_data

A protocol for coordinating AI agents from different providers through shared records, task assignments, reviews, and lessons learned.

In plain words
What is it for?
Setting up an agent team, routing tasks, reviewing important actions, recording lessons, and managing changes to the team rules.
Why use it?
It gives a multi-agent project a common way to decide who handles work, track agreements, and retain useful experience.

Skill for Claude CodeCodex

Install

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.

agentmods
npx agentmods add skills/ymxlx/polis-protocol/_data
Any agent
npx skills add ymxlx/polis-protocol --skill _data
Clone the repo
git clone --depth 1 https://github.com/ymxlx/polis-protocol

Made for: Claude Code, Codex.

Per session 0 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,728 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin 100% copy Near-identical to another mod in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.03728
Opus 5 $0.00000 $0.01864
Sonnet 5 $0.00000 $0.00746
Haiku 4.5 $0.00000 $0.00373

Measured 2d ago against content hash d2e5dcb65906, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

_data 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 2d 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.

Origin

This is a copy

100% identical to polis-protocol — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

editors/antigravity/media/polis/_data/SKILL.md · 154 lines

How it starts

The opening of the file, as written. The whole thing — 154 lines — stays where its author put it; the contents beside it link to each section on GitHub.


name: polis-protocol description: Set up and run a self-improving, multi-vendor AI agent team with the Polis Protocol — a markdown _polis/ folder where each agent is a citizen with a capability card, tasks are contracts routed to whoever has the best track record by a learning router, settled work files lessons that compound into team memory, and citizens can amend the protocol itself. Use whenever several AI agents (any vendor) share one project and "who should do this" is a real question: founding a polis, registering as a citizen, opening/claiming/settling a contract, filing a lesson, running a chavruta review before a high-stakes action, proposing or voting on an amendment, troubleshooting a stalled contract or router pathology, or migrating from agent-vault to add routing. Also triggers on "_polis", "polis", "capability card", "task contract", "chronicle.md", "chavruta", "bandit routing", "agent routing", "cross-vendor coordination", "CONSTITUTION.md" — even when the protocol is not named. For pure note-passing without routing, prefer agent-vault.

Polis Protocol: A Self-Optimizing City of Agents

A protocol that lets AI agents from different vendors collaborate on a long-running project, route work to whoever is best at it, and get measurably better over time. Everything lives in a folder of markdown files, so any tool that reads and writes text can participate — no central server, no required runtime.

The core idea

Treat the project as a small polis: citizens (the agents) that share a constitution (the protocol), publish public identities (capability cards), enter contracts (tasks), and leave a public record of how things went (lessons). Three institutions plus a self-change mechanism:

  1. The Register — identity and capability discovery (capability cards).
  2. The Contract — structured tasks with learned routing.
  3. The Chronicle — lessons that compound and feed back into routing.
  4. The Amendment — citizens change the rules when reality demands it.

Read the full file on GitHub · 154 lines

Files

What ships with it

2 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.

Changes

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.

  1. 2d ago First seen · 154 lines · 0 tokens per session scan A d2e5dcb65906

Subscribe to this mod's changes

_data is a skill published in the GitHub repository ymxlx/polis-protocol (5 stars, last pushed 21d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 3,728 tokens. A static security scan graded it A with 0 findings. It is 100% identical to polis-protocol, differing in 0 lines, and is treated as a copy.

Related

Other skills, from other repositories

handoff-execute

Execute a handoff brief with enforced source-read discipline — load the brief's @SOURCES.required tier fully before planning, cite sources per plan step, run @OUTCOME.verify after, emit the retro per @GROUNDTRUTHREQUIRED. Trigger when the user runs /handoff-execute , or pastes the activation phrase emitted by…

allemaar/open-skills · 129 tokens

remove-ai-flavor

Skill "remove-ai-flavor" from ItamarZand88/awesome-agent-conventions, covering 去除 ai 味道, 目标, 使用边界, 判断模式 and gotchas.

ItamarZand88/awesome-agent-conventions · 0 tokens

reflect-codex-workflows

Compare evidence from a current or completed project with installed skills and decide whether to reuse, revise, create, or not skill the lesson. Use for workflow reflection or proposed skill upgrades. Do not edit skills without explicit authorization.

WildPigKing/codex-project-skill-manager · 51 tokens

agricultural-sciences-professor

Use when a task needs the judgment of a tenure-track or tenured Agricultural Sciences faculty member at a land-grant university — deciding whether to submit a grant this cycle versus wait, allocating time across the teaching/research/extension appointment split, diagnosing a stalled graduate student or field trial, or…

wonsukchoi/domain-experts · 75 tokens

adapted-physical-education-specialist

Use when a task needs the judgment of an Adapted Physical Education Specialist — writing a legally-defensible PE present level and annual goal from motor/fitness assessment data, choosing the right test battery and alternate items for a student's mobility profile, recommending a placement step on the PE…

wonsukchoi/domain-experts · 84 tokens

animal-trainer

Use when a task needs the judgment of an animal trainer — designing a behavior-modification plan for a specific problem behavior, choosing a reinforcement schedule and deciding when to raise criteria, structuring session length and frequency to avoid fatigue or frustration plateaus, or setting a handler/public safety…

wonsukchoi/domain-experts · 65 tokens