Agent Plugins standardizes portable agent packages

The most important part is the deliberately boring packaging layer: shared conventions could matter more than another agent framework.

• –A filesystem-based format lets developers write skills and MCP integrations once, then adapt them across clients
• –Fixed locations and JSON schemas make discovery and validation predictable
• –Reverse-domain extensions preserve room for client-specific features without fragmenting the core standard
• –The format reduces packaging friction but does not solve marketplace discovery, permissions, trust, or malicious plugin risk
• –Broad industry backing gives the specification a credible chance of becoming shared infrastructure rather than another vendor format