Skip to main content
Trust and scope | Agent PluginsTrust and scope in the source-owned Agent Plugins documentation.Agent Pluginsreferenceagentpluginsreferenceadopterdeveloperbuild-agent-systemstry-spec-driven-developmentreference

What installation does—and does not—mean

Plugins are instruction bundles. They shape how an agent approaches a task, but they do not carry credentials and cannot enlarge the authority granted by the host, operator, or repository.

Every published plugin is intentionally narrow:

  • Beyond10x routes work, links public resources, and creates portable plugins without copying the specialist workflows.
  • AEP Plan governs planning artifacts and lifecycle-aware planning work.
  • AEP Drive coordinates accepted development work.
  • ESS Specify specifies, validates and projects executable system contracts.

The repository gate checks that the two marketplace formats agree in their declared order, plugin and directory names match, required skills and agents exist, and no retired marketplace or source-repository identity reappears. Release tags also pin every plugin manifest to the workspace version.

Review the source before installation and pin a release tag when repeatability matters.