[Feature Request] Support the Agent Plugins specification (agent-plugins.org) package format

Background

Agent Plugins (agentplugins/agent-plugins-spec) is an open, vendor-neutral standard for packaging reusable agent components (Agent Skills + MCP servers) into distributable plugins. Spec 1.0.0 is published, and packages in this format are starting to appear across the agent ecosystem.

Kimi Code CLI currently only recognizes its own plugin manifest format, so plugins published in this vendor-neutral format cannot be installed via /plugins install. Since both formats build on the same Agent Skills (SKILL.md) component model, the gap is mainly in manifest/discovery conventions rather than in the components themselves.

Suggestion

Consider supporting the Agent Plugins package format — for example, by falling back to the standard manifest when no Kimi-specific manifest is present, so spec-conformant plugins become installable out of the box while Kimi-specific capabilities (hooks, commands, session start, etc.) remain available through the existing Kimi manifest. Full client conformance per the spec could be a longer-term goal.

This would let Kimi Code users benefit from the growing ecosystem of vendor-neutral plugins, and let plugin authors target Kimi Code without maintaining a separate package.

References

• Spec: https://github.com/agentplugins/agent-plugins-spec (v1.0.0)
• Kimi Code plugin docs: https://www.kimi.com/code/docs/en/kimi-code-cli/customization/plugins.html

Start at the /plugins install entry point and read the Kimi Code plugin documentation, then compare its manifest and discovery rules with Agent Plugins spec v1.0.0. Done means a spec-conformant package can be installed when no Kimi-specific manifest is present, while existing Kimi manifest capabilities continue to work; the payload names no source files or tests.