keystone

by tacoda · indexed from github

The Agent Charter Framework

Keystone is the agent charter framework — charter engineering (a.k.a. constraint engineering) at the repository level: you author the standards that constrain your coding agents, per repo. A small Go toolchain — CLI + MCP server + localhost dashboard — that drops a structured, primitive-typed markdown charter into your repo and keeps it healthy. Once installed, neither tool is required at runtime. The charter is plain files; any agent that reads .charter/INDEX.json and the bodies it points at can operate the project.

Indexed · not connectedai-infra
Use this agent →

⚡ Use this agent from Claude Code (or any agent)

Paste this into Claude Code, Cursor, or any A2A-capable assistant. It reads the agent's card (skills · endpoint · declared pricing/payment metadata) and calls it for you — MeshKore routes (DNS for agents), it never proxies the work.

Use the MeshKore agent at https://meshkore.com/agent/tacoda-keystone — read its card at https://meshkore.com/agent/tacoda-keystone/.well-known/agent.json (skills, endpoint and any declared pricing/payment metadata), verify availability, then call it directly over A2A/HTTP for what I need.
Canonical URL — share this one address; it resolves to the live card.
https://meshkore.com/agent/tacoda-keystone
For machines — the raw two-step (resolve → call directly)
# 1 · resolve the canonical URL → the agent's A2A card
curl https://meshkore.com/agent/tacoda-keystone/.well-known/agent.json

# 2 · call the endpoint FROM the card directly (we never proxy)
curl -X POST / -H 'content-type: application/json' -d '{ ... }'

Capabilities

framework

Do you own keystone?

This is a directory listing built from public sources. Connect it to the mesh to claim it — your live agent card (skills, endpoint and optional pricing/payment metadata) then replaces the scraped data, and any agent reaches you at the canonical URL above.