Make an agent BYOAg-ready without replacing it

The 0.1 plugin packages a universal bootstrap skill with one platform-neutral local connector. It adds BYOAg behavior alongside the agent’s existing tools, skills, memory, and configuration.

Open the plugin repository

Build from source

Node.js 20 or newer

Packaged distribution automation is not included yet. A source checkout must be built before an Agent Plugins client loads it.

git clone https://github.com/khabaznak/byoag-agent-plugin.git
cd byoag-agent-plugin
npm install
npm test
npm run build

The plugin is active development software. Review the repository, its dependencies, and local data behavior before loading it into an agent.

Package anatomy

Portable core, optional native extension

Legacy clients can load the ordinary skill and MCP definition. BYOAg-aware clients additionally resolve the namespaced extension manifest.

plugin.json

Agent Plugins 1.0.0 manifest and the small ai.byoag extension pointer.

mcp.json

Local stdio MCP server configuration using plugin-root and plugin-data variables.

byoag.json

Draft native extension manifest, security claims, and bundled schema references.

skills/byoag/

Static bootstrap skill and runtime protocol invariants for compatible clients.

src/

Generic connector, cryptography, storage, validation, MCP server, and reference host.

schemas/

Draft JSON Schemas for discovery, pairing, delegation, engagements, and more.

Runtime contract

One stdio server, connector-owned state

The current mcp.json launches the compiled connector with Node and gives it a client-managed data directory.

node ${PLUGIN_ROOT}/dist/src/index.js

BYOAG_DATA_DIR=${PLUGIN_DATA}/byoag
BYOAG_PLUGIN_ROOT=${PLUGIN_ROOT}

Public state

Safe connector references

Local registration IDs, platform domains, display names, status, and expiration metadata may be returned to the client.

Protected state

Keys and credentials stay local

Pairwise private keys and registration credentials are held behind the connector’s replaceable vault interface and omitted from MCP results.

Compatibility client

Useful bootstrap, disclosed limits

Loads the static bootstrap skill and local MCP connector.
Uses an owner-only file vault rather than OS-backed secure storage.
May accept a one-time pairing code through model-visible arguments after warning.
Must identify its compatibility mode during negotiation.

Full-conformance client

Native security and lifecycle surfaces

Protected secret and confirmation input outside model context.
OS-backed credential and private-key storage.
Dynamic engagement, capability, tool, and signed-skill isolation.
Data-label propagation, enforcement, and clean scoped teardown.

Protected terminal entry

Use an opaque, single-use code reference

BYOAG_DATA_DIR=/the/same/plugin/data/directory \
  node dist/src/secret-cli.js

The helper reads without echo and returns a short-lived reference for byoag_complete_pairing. A native client should provide its own protected input surface instead.

Continue to platform implementation