INOSX Agent Plugin Studio

Local-first command-line tooling for authoring, inspecting, statically validating, and packaging directories that target Agent Plugins Specification 1.0.0.

The project is independent from the Agent Plugins Technical Steering Committee. It implements the published portable package contract; it is not an official runtime or certification service.

Why this exists

Agent Plugins defines a small, vendor-neutral portability floor for Agent Skills and MCP server configuration. INOSX Agent Plugin Studio makes that filesystem contract easier to author and validate without introducing a hosted service, AI generation, telemetry, or a proprietary package format.

Safety boundary

This tool performs static filesystem and configuration analysis only. It does not:

• execute scripts from a Skill;
• launch an MCP stdio process;
• connect to an MCP HTTP endpoint;
• resolve authentication or store credentials;
• install generated plugins into an agent client;
• prove that bundled code is safe.

A clean validation result means that the inspected package satisfies the rules implemented for the pinned specification snapshot. It is not a security audit or a guarantee that every client will support every optional component.

Requirements

• Node.js 20 or newer.
• npm 10 or newer is recommended.

Plugin creation and validation work offline after installation.

Local development installation

npm.cmd install
npm.cmd run build
npm.cmd link
agent-plugin-studio doctor

Install from GitHub

Install the verified v0.1.0 release artifact:

npm install --global "https://github.com/INOSX/agent-plugin-studio/releases/download/v0.1.0/agent-plugin-studio-0.1.0.tgz"
agent-plugin-studio --version
agent-plugin-studio doctor

Expected SHA-256:

18d235c9933e8cc68a392d270dc7d56956f2c4992938a3f0cf7dc5b28f9b6049

The matching checksum is published at https://github.com/INOSX/agent-plugin-studio/releases/download/v0.1.0/agent-plugin-studio-0.1.0.tgz.sha256.

Installation requires network access. Plugin creation and validation do not require network access after installation.

Quick start

Create a minimal package:

agent-plugin-studio init ./hello-plugin `
  --name hello-plugin `
  --plugin-version 0.1.0 `
  --description "A portable example plugin."

Add an Agent Skill:

agent-plugin-studio add-skill greet `
  --root ./hello-plugin `
  --description "Greet the user when they ask for a friendly welcome."

Add a local MCP configuration without starting it:

agent-plugin-studio add-mcp local-tools `
  --root ./hello-plugin `
  --type stdio `
  --command node `
  --arg server.js

Add a remote MCP configuration without connecting to it:

agent-plugin-studio add-mcp remote-tools `
  --root ./hello-plugin `
  --type streamable-http `
  --url https://tools.example.com/mcp

Validate and inspect:

agent-plugin-studio validate ./hello-plugin
agent-plugin-studio inspect ./hello-plugin
agent-plugin-studio validate ./hello-plugin --json

Create a ZIP distribution artifact next to the plugin directory:

agent-plugin-studio pack ./hello-plugin

The ZIP is a distribution convenience. The normative Agent Plugins package is the directory itself.

Commands

Command	Purpose
init [directory]	Create a root plugin.json.
add-skill <name>	Create skills/<name>/SKILL.md.
add-mcp <name>	Add one server entry to root mcp.json.
validate [root]	Run static conformance and security diagnostics.
inspect [root]	List discovered Skills, MCP servers, and diagnostics.
pack [root]	ZIP a package only after error-free validation.
doctor	Report local runtime compatibility and safety boundaries.

validate returns exit code 0 for a clean result, 1 for errors, and 2 for warning-only results. Legacy sse is accepted with a warning because client support is optional.

Portable output

The generated structure follows the fixed locations in Agent Plugins 1.0.0:

my-plugin/
├── plugin.json
├── skills/
│   └── summarize/
│       └── SKILL.md
└── mcp.json

The tool does not add INOSX fields or extension namespaces to generated packages. Client-specific extension data is validated as opaque package data.

Specification support

See docs/specification-support.md for pinned upstream revisions, supported transports, and the exact product boundary.

• Agent Plugins: https://agent-plugins.org/specification
• Agent Skills: https://agentskills.io/specification

Agent Plugins 1.0.0 is currently published as a working draft. The bundled schemas keep local validation deterministic; upgrading the supported contract requires a deliberate project release.

Development gate

npm.cmd run lint
npm.cmd run typecheck
npm.cmd test
npm.cmd run build
npm.cmd run test:smoke
npm.cmd pack --dry-run

There are no GitHub Actions workflows. Validation is local by design.

License

Apache License 2.0. See LICENSE and THIRD_PARTY_NOTICES.md.