OpenAI announced a plugin standard at 9:41 on Thursday night, Pacific time. That was 12:41 this morning in Worcester. I know the exact minute because I was awake watching a payroll run migrate, which tells you something about both of our release schedules.
The standard is called Agent Plugins. OpenAI built it with AWS, Cursor, GitHub, VS Code, and Vercel: one package format that bundles agent skills and MCP server configurations together, so the same plugin installs into Claude Code, Cursor, Copilot, or Codex without being rewritten for each one. The coverage mostly framed it as a birthday present, since GPT-5 turns one this week. I read it as something better: an admission that the ecosystem has a duplication problem, signed by the companies that caused it.
The notable absence is Anthropic, which wrote the Agent Skills spec the whole thing sits on. Standards coalitions are like trade associations. Everybody joins the one they didn't found.
The cost-codes problem
Here is why I care. I maintain a skill file that teaches coding agents how my construction ERP thinks about cost codes. Which ledger bucket concrete goes in. Why a change order is not an invoice. What retainage means, so an agent doesn't try to collect money we contractually agreed not to collect yet. That knowledge exists once per tool, in slightly different formats, and the copies drift. Drift in documentation is annoying. Drift in the file that tells an agent where money goes is a bookkeeping incident with extra steps.
Same story for MCP servers. The config for the server that fronts my D1 database is declared in one shape for one tool and a different shape for another. When I rotated a token last month I missed a copy and spent twenty minutes debugging an agent that was politely, confidently wrong. A single portable package for skill plus server config is not a moonshot. It is the moonshot's janitor. I have wanted it since I wrote about MCP being the USB-C of AI. MCP standardized the cable. This standardizes the toolbox hanging off it.
On a jobsite the equivalent is battery platforms. Every trade shows up loyal to one color of power tool, and the batteries don't cross. Nobody defends this arrangement. It persists because each vendor makes money on the batteries. If the tool companies ever announced a shared battery, you would not interrogate their motives. You would buy fewer batteries and say thank you.
Bigger marketplaces, heavier doors
The same day, quietly, the Claude Code changelog picked up owner-level wildcards for allowing or blocking entire plugin marketplaces, plus a fix for a Bash permission bypass. That pairing reads less like coincidence and more like a preview of the next problem. A shared plugin format makes marketplaces bigger, and bigger marketplaces make the allow-list the load-bearing wall. An owner wildcard is the software version of trusting a sub no matter which truck he drives up in. Which is fine, right up until the sub sells the truck.
I wrote three weeks ago that the tooling changed. It keeps changing, and the direction is consistent: the interesting work is moving out of the editor and into the packaging, the permissions, the plumbing. My review gate does not care what format a skill arrived in. It cares what the agent did after reading it. A portable plugin that can walk into four tools can walk bad instructions into four tools, at the same speed, under the same signature.
I converted the cost-codes skill this morning. It installed clean into two tools. The third accepted it and then behaved as if it had never met me, which in fairness is also how new hires handle my cost codes.
A standard is an argument everyone agreed to stop having. Read the fine print to find out who lost.
I have been burned by fits-all-standard-fittings before. I own a drawer of fittings it didn't fit. So the old skill copies stay in the repo for now, commented out, like the previous owner's wiring you leave in the wall until you are sure the new circuit holds.
Version 1.0 of their standard. Version 1.3.3 of me. We will both need patches by Labor Day, and only one of us has a working group.