OpenAI and Rivals Publish Agent Plugins: One Package Format for AI Agents

OpenAI, Amazon, Microsoft, Cursor, and Vercel just published Agent Plugins 1.0, an open standard for packaging AI agent extensions. The pitch: build once, run anywhere. Instead of each tool expecting different folder layouts and setup, Agent Plugins defines a single package format.
A plugin is just a folder with a plugin.json file at its root. It bundles two things developers already use:
- Model Context Protocol (MCP) servers — connect agents to live tools and data.
- Agent Skills — reusable sets of instructions.
At launch, ChatGPT, Codex, Cursor, GitHub Copilot, Kiro, and VS Code support the format. The spec is openly licensed; no single company's roadmap steers it.
Deliberately minimal
The standard intentionally avoids the hard parts. Marketplaces, installation, permissions, sandboxing, and trust remain client-specific. That keeps adoption low-friction, but it also means deciding whether a plugin is safe to run is still every client's job — a live concern after fake Agent Skills slipped past security scanners earlier this year.
Not everyone is sold. Dax Raad of SST called it “a thin standard” whose useful parts will end up in client-specific extensions anyway. Others like Angie Jones welcomed it: “We neeeeded this.”
What it means for you
If you build agent skills or MCP servers, you can now package them once and reach a wide range of tools. The competitive landscape shifts too: a shared format helps small devs reach major clients, but it also cements whichever clients already have the users. The plumbing is agreed — the fight over marketplaces and trust is just beginning.
📖 Read the full source: HN LLM Tools
👀 See Also

AI Is Making Me Dumb: A Developer's Confession of Skill Atrophy
James Pain confesses that after a year or two of using AI exclusively for coding (no hand-written code), he has mostly forgotten how to code. He's now teaching himself to code by hand again, and warns that heavy AI use can erode writing and coding skills.

Agentic Coding Is a Trap: Cognitive Debt and Atrophy
Lars Faye argues that agentic coding tools like Claude Code cause cognitive atrophy, vendor lock-in, and increased complexity, shifting the burden from writing code to reviewing generated code, which degrades developer skills.

Analyzing Claude's 1M Context Window Token Burn: Data Shows Unbounded Growth and Cache Miss Compounding
Analysis of Claude's 1M context window reveals two compounding factors causing rapid token consumption: unbounded context growth without auto-compaction and expensive cache misses at larger context sizes. The author provides a Python script to analyze personal token usage from JSONL session files.

Coding Agents Supersede Human Code Review: Paper Argues Traditional Review Is Dead
arXiv paper argues coding agents have crossed the threshold to replace human code review, offering lower cost and higher throughput.