Anthropic defined the standards inside Agent Plugins. So why isn’t it helping govern the format?

Sicherheitsmeldung mit Schweregrad hoch. Sie wird laut CISA-KEV aktiv ausgenutzt und sollte priorisiert behandelt werden. Technische Details im Tab „Originaltext“; empfohlene Schritte in der Checkliste.

Originaltext der Quelle (nicht übersetzt) – die deutsche Zusammenfassung findest du im Tab „Kurzfassung".

Earlier this month, Vercel released Agent Plugins 1.0.0 with core maintainers from AWS, Cursor, Microsoft, and OpenAI. Google announced the same day that it was joining them. The format fixes something that genuinely annoys developers: A skill and an MCP server that work fine on their own still have to be forked and maintained twice the moment you ship them to a second client.

Though the six companies agreed on where components live, they don’t standardize on what they do. Section 7.1 of the spec hands the skill format to the Agent Skills specification. Section 7.2 hands wire behavior and lifecycle to MCP. Both came out of Anthropic, which released them openly but does not sit on the steering committee.

The project is candid about this. Its own documentation calls the result a small interoperability floor, and Google’s post describes v1 as a package format and nothing more. The obvious discrepancy is not between promotional rhetoric and technical truth. Rather, the issue is that terms like “compatible,” “portable,” and “plugin” suggest much more in everyday use than this narrow agreement actually provides.

What Anthropic released, and to whom

Anthropic donated MCP to the Agentic AI Foundation, a Linux Foundation-directed fund, on 9 December 2025. Agent Skills followed nine days later, published as an open standard and now developed in the open at agentskills.io. The governance stories differ. MCP belongs to an independent foundation, while Agent Skills is an openly developed specification without a comparable legal steward.

The Agent Plugins project lacks authority …

Vollständiger Originalartikel ↗

• Betroffenheit im eigenen Stack prüfen: Versionen/Komponenten abgleichen.
• Originalquelle / Hersteller-Advisory lesen: https://thenewstack.io/agent-plugins-portability-gaps/
• Priorität HOCH: laut CISA-KEV aktiv ausgenutzt – bevorzugt patchen.
• Verfügbaren Patch oder Workaround einspielen und dokumentieren.
• Erkennung: Logs und Indikatoren (IoCs) auf Ausnutzung prüfen.