How to Test AI Agents Without Vendor Lock-in — Introducing ABS

You know the drill. QA opens a Word doc, types "the bot should ask for the order number if it's missing," and tests the agent by hand. Meanwhile, Dev builds against an ever-mutating PR description. And PO has nothing to sign off on that isn't prose or code.

We solved this for APIs 20 years ago with OpenAPI. A shared contract. Machine-readable.Tool-independent. Human-auditable.AI agents have no equivalent. Until now.

What ABS is — in 30 seconds

Agent Behavior Specification (ABS) is a YAML format for describing observable agent behavior — messages, tool calls, hand-offs, UI interactions — independent of your LLM provider, framework, or tool protocol.

One file. Three stakeholders. Two modes: descriptive and executable.

How to Test AI Agents Without Vendor Lock-in — Introducing ABS

Related reading

Test smarter with Snagly: 30 open-source QA skills for AI coding agents

The release gate I would add before letting an AI agent touch ERP workflows

Visual QA Agents: Catch UI Regressions Before AI-Written Code Ships

AI Test Agents Are Useful, but Only If You Keep Them on a Leash

Giving an AI Coding Agent a Job Without Giving It Your Credentials

Why AI Agents Keep Breaking Your Code — And What to Do About It