Interesting approach — treating agent definitions the way Kubernetes treats infrastructure. The core idea is that your agent's identity, tools, constraints, and execution strategy all live in a single .agf.yaml file, and any runtime (LangChain, ADK, whatever) can execute it via adapters.

The engineering blog goes deeper into the motivation: https://eng.snap.com/agent-format

A few things that stood out to me:

The schema is grounded in POMDP formalism, which gives it a principled foundation rather than being yet another config format

There's a "tighten-only invariant" for multi-agent systems — child agents can never exceed their parent's constraints. Governance gets stricter as you go deeper, never looser

It explicitly separates agent-level constraints from org-level policies. The runtime composes both at execution time

They position it alongside MCP (tools) and A2A (agent communication) — three complementary layers rather than competing standards

The JSON Schema is published, there's an interactive playground on the site, and the spec itself is vendor-neutral. Curious if anyone has tried plugging this into their own stack.