agentpluginsdirectory

Verified

Kiro Powers and Agent Plugins

All 2,765 verified Agent Plugins install in Kiro, where they are called Powers. Kiro Powers follow the Agent Plugins specification, so any repository with a root plugin.json installs as one — the naming differs, the format does not. What is specific to Kiro is the three entry points: Add Custom Power, Import power from GitHub, and Add to Kiro on kiro.dev/powers.

Start here

These are the ten most-starred repositories publishing verified Agent Plugins, one row each so a single bundle publisher cannot fill the table. Every one of them installs in Kiro — the catalogue is identical for all six clients, which is the point of a portable format. The full directory carries all 2,765, filterable by category, skills and MCP servers.

Plugin Publisher Skills MCP Stars
worldmonitor koala73 25 2 87,129
context7 upstash 1 1 62,267
chrome-devtools ChromeDevTools 7 1 52,414
agentic-bundle-aas-accessibility-inclusive-ux (+36) sickn33 308 0 46,689
scientific-agent-skills K-Dense-AI 166 0 45,870
daisyui saadeghi 1 0 42,441
openviking volcengine 3 1 38,289
diffusers huggingface 4 0 34,555
aihawk feder-cr 1 1 31,614
pascal-agent-skills pascalorg 2 1 24,180

Powers are Agent Plugins

Kiro calls them Powers. The Powers documentation says they "adhere to the Agent Plugins specification," described there as "an open, vendor-neutral format for packaging reusable components that extend AI agents," and states the portability case as "Build once and your power works across compatible agent clients."

A power's layout is the standard layout:

  • plugin.json, "the manifest that identifies the power and declares its keywords for activation"
  • skills/, holding Agent Skills with their instructions, scripts, and reference material
  • mcp.json, optional, for MCP server configuration
  • dev.kiro/, optional, holding Kiro-specific extensions such as steering files

That last directory is the reverse-domain extension namespace at work. Other clients ignore dev.kiro/ and load the rest.

Install from kiro.dev

  1. Browse powers at kiro.dev/powers.
  2. Select a power and click Add to Kiro.
  3. The IDE opens to complete the installation.

Install from inside the IDE

  1. Open the powers panel by clicking the ghost icon with the lightning bolt.
  2. Choose a power to view its details.
  3. Select + Install.

After installing, Try the power runs its onboarding.

Install from a GitHub repository

This is the route for anything you find in this directory:

  1. Open the powers panel and select Add Custom Power.
  2. Select Import power from GitHub.
  3. Enter the repository URL.
  4. Click Install.

The repository must contain a valid plugin.json or POWER.md at its root, per Kiro's installation docs.

Install from a local folder

  1. Powers panel, then Add Custom Power.
  2. Select Import power from a folder.
  3. Select the directory containing plugin.json or POWER.md.
  4. Click Install.

To update a power later: open the Powers panel, select the power, choose Check for updates, then Install updates.

What Kiro does with MCP servers

Kiro accepts both the Agent Plugins format and its own legacy POWER.md format, and it handles their MCP servers differently. A power in the Agent Plugins format has its MCP servers managed internally by Kiro. A legacy-format power registers them in ~/.kiro/settings/mcp.json instead. If you are looking for a plugin's server in that file and cannot find it, the plugin is probably the portable kind.

The spec's compatible clients page records Kiro as loading Agent Skills plus MCP over stdio, Streamable HTTP, and legacy HTTP+SSE.

Verified plugins worth trying

AWS ships Agent Plugins support in both Kiro and the AWS Agent Toolkit, described in its open source blog post as "a collection of official AWS-supported MCP servers, skills, and agent plugins."

According to agentpluginsdirectory.com's verified index, 2026-08-08, the aws organization publishes 4 verified plugins across a repository holding 2,269 stars. Two more, confirmed by fetching their manifests and validating them against the official 1.0.0 schema:

  • agentic-bundle-aas-devops-cloud (sickn33/agentic-awesome-skills, 44,651 repo stars), 10 skills.
  • agentic-bundle-aas-observability-ir (same repository), 10 skills covering observability and incident response.

agentpluginsdirectory.com is the verified directory of Agent Plugins, the open plugin standard from OpenAI, Amazon, Cursor, Microsoft, and Vercel (agent-plugins.org) supported by ChatGPT, Codex, Cursor, GitHub Copilot, VS Code, and Kiro. Every listing is verified by fetching its plugin.json manifest and checking it against the official 1.0.0 schema.

Plugin counts verified on 2026-08-08. Install steps verified against Kiro's documentation on 2026-08-07.

Next: the install hub for the other five clients, the full plugin directory, or how to build an Agent Plugin.