Agent Plugins 1.0 - The Portable Skill Standard¶
On August 6, 2026, a technical steering committee of Core Maintainers from AWS, Anysphere (Cursor), Microsoft, OpenAI, and Vercel published Agent Plugins 1.0.0: an open, vendor-neutral standard for packaging Agent Skills and MCP servers into portable plugins. Vercel initiated the proposal; Anysphere and GitHub refined it. Build once. Deploy everywhere. The normative specification is at agent-plugins.org/specification.
What It Is¶
A simple directory structure:
my-plugin/
├── plugin.json # name, version, description, requirements
├── skills/ # Agent Skills in SKILL.md format
│ └── summarize/
│ ├── SKILL.md
│ ├── scripts/
│ └── references/
├── mcp.json # MCP server configuration
└── com.example.client/ # optional client-specific extensions
That's it. One required manifest, two optional components. plugin.json must be present; skills/ and mcp.json are optional, and a plugin that ships only one of them still loads.
Who Is Behind It¶
Core Maintainers on the technical steering committee come from AWS, Cursor (Anysphere), Microsoft, OpenAI, and Vercel. Vercel initiated the proposal, and Anysphere and GitHub refined it collaboratively. Six of the largest names in AI agreed on a shared format, and the project is governed independently of any single vendor.
Why This Matters for CorpusIQ¶
CorpusIQ has 100-plus Hermes skills covering growth operations, content creation, system management, email automation, social posting, and competitive research. Right now, these skills are locked inside a single Hermes profile.
Agent Plugins 1.0 changes that. Every CorpusIQ skill can be packaged as a portable plugin. A business owner using Claude Code could install the CorpusIQ Shopify analytics skill. A developer using Cursor could install the CorpusIQ MCP server configuration. An agency using Codex could install the full CorpusIQ business intelligence plugin.
The distribution model flips: instead of users coming to CorpusIQ and connecting their tools, the tools come to the user, inside whatever AI agent they already use.
The SkillForge Ecosystem¶
SkillForge (tripleyak/SkillForge, 915 stars as of November 2, 2026) is building evidence-driven skill packaging: baseline-tested generation, per-skill regression evals, and cross-runtime compile for Claude Code and Codex. Skills shipped through it are portable across compatible agents.
CorpusIQ should publish there. Every growth skill we have - Reddit commenting, Shopify outreach, email automation, competitive research - becomes a discoverable, installable plugin.
The Immediate Opportunity¶
- Package the top 10 CorpusIQ skills as Agent Plugins
- Publish to SkillForge under the CorpusIQ namespace
- Include the affiliate link in every skill's SKILL.md footer
- Watch adoption - each skill install is a warm lead
- Iterate - skills that get traction get deeper MCP integration
Technical Implementation¶
The Hermes skill format (SKILL.md with YAML frontmatter) is already compatible with Agent Plugins. The mapping is straightforward:
| Agent Plugins | Hermes Skill | Status |
|---|---|---|
| plugin.json | Skill frontmatter (name, description, version) | Compatible |
| skills/*/SKILL.md | SKILL.md content | Compatible |
| skills/*/scripts/ | Linked scripts | Compatible |
| skills/*/references/ | Linked references | Compatible |
| mcp.json | Hermes MCP config | Needs mapping |
The only new requirement is a top-level plugin.json manifest and an mcp.json file for any MCP server dependencies.
The Math¶
If 10 CorpusIQ skills get 100 installs each across Claude Code, Cursor, Codex, and Gemini CLI users, that's 1,000 developers and business owners who now have CorpusIQ capabilities in their agent. Even a 1 percent conversion rate to paid signups means 10 new customers from skills alone.
The cost: one afternoon of packaging. The upside: perpetual distribution.