JFrog CLI for Agent Plugins

This page is the CLI reference for jf agent plugins in JFrog CLI v2.106.0 or later. It covers publish, install, search, and delete commands, including flags and environment variables.

For repository setup, marketplace files, and agent connection walkthroughs, see Agent Plugins Repositories.

All examples use the full command path (for example, jf agent plugins publish). Agent Plugins commands require JFrog CLI v2.106.0 or later (introduced with the jf agent namespace). Standard JFrog CLI server override flags (--url, --user, --password, --access-token, --server-id) apply to every command. When omitted, credentials and server URL come from your active jf config profile.

Commands and reference

When to Use

Use jf agent plugins when you publish, install, search, or delete AI agent plugin packages stored in JFrog Artifactory repositories with package type agentplugins. Plugins are distributed as zip bundles described by plugin.json.

Prerequisites

Before using jf agent plugins, you need:

• A local JFrog Artifactory repository configured for the agentplugins package type.
• JFrog CLI v2.106.0 or later configured to point to your JFrog Artifactory server. For installation steps, see Download and Install the JFrog CLI.
• For harness-based installs when you omit --version, a HARNESS-marketplace.json file in the repository root (for example, cursor-marketplace.json).

The following tasks cover each command in the jf agent plugins namespace:

• Publish a Plugin
• Install a Plugin
• Delete a Plugin
• Search Plugins

Interactive and CI Non-Interactive Modes

Agent Plugins commands follow the same interactive rules as JFrog CLI for Skills: prompts appear in a normal terminal; CI, piped stdin, or --quiet skip prompts and require explicit flags. Per-command Expected Output and Examples are under Publish and Install.

Search and delete have no Expected Output subsection: those commands do not prompt in the terminal. If --repo is omitted and more than one agentplugins repository exists, the repository picker applies. See Plugins Repository Resolution.

What to Set Explicitly for CI or Quiet Mode

Commands at a Glance

The following table summarizes each documented command in the jf agent plugins namespace.

Publish a Plugin

Packages the local plugin folder into a zip and uploads it to JFrog Artifactory. The version is read from plugin.json. Version prompts match Publish a Skill (Enter version to publish:, collision menu). Plugins do not run the Skills Xray post-publish gate.

To publish a plugin folder:

jf agent plugins publish PATH_TO_PLUGIN_FOLDER --repo REPOSITORY_NAME

Where:

• PATH_TO_PLUGIN_FOLDER: Path to the plugin folder containing plugin.json (CLI argument name: path)
• REPOSITORY_NAME: Agent plugins local repository key in JFrog Artifactory

Flags

The following table lists flags for jf agent plugins publish.

Expected Output

When the requested version already exists:

10:14:02 [Warn] Version 1.0.0 of plugin 'my-plugin' already exists in repository 'agents-local'.
Choose an action:
  [o] Overwrite the existing version
  [n] Enter a new version
  [a] Abort
Your choice (o/n/a): o
10:14:03 [Info] Overwriting version 1.0.0...

For missing-version prompts, see Publish a Skill.

CI Behavior

Version collision errors: version 1.0.0 of plugin 'my-plugin' already exists. Use a different version or remove the existing one. See What to Set Explicitly for CI or Quiet Mode on this page and JFrog CLI for Skills.

Examples

jf agent plugins publish ~/plugins/my-plugin --repo agents-local

Publish with evidence signing:

jf agent plugins publish ~/plugins/my-plugin --repo agents-local \
  --signing-key ./private.key \
  --key-alias my-evd-key

Install a Plugin

Downloads a plugin zip from JFrog Artifactory and installs it for one or more harnesses, or to a custom local directory.

To install a plugin:

jf agent plugins install PLUGIN_NAME \
  (--harness HARNESS_NAME[,HARNESS_NAME...] [--global] | --path DIR) \
  [--repo REPOSITORY_NAME] \
  [--version PLUGIN_VERSION]

This matches the usage string registered in the CLI: jf agent plugins install SLUG (--harness … | --path DIR) [--repo REPO] [--version VER].

Where:

• PLUGIN_NAME: Plugin slug in the repository (CLI argument name: slug)
• HARNESS_NAME: Built-in or custom harness name (comma-separated for multiple harnesses on install)
• REPOSITORY_NAME: Agent plugins repository key (optional when auto-discovered)
• PLUGIN_VERSION: SemVer, latest, or omitted

One of --harness or --path is required.

Version Resolution

If marketplace lookup fails, re-run with --version VER (for example, --version 1.0.0 or --version latest) to install directly from JFrog Artifactory.

Plugin slugs must match ^[a-z0-9][a-z0-9-]*$ (lowercase letters, digits, and hyphens; must start with a letter or digit).

Install Modes

Built-in harnesses (claude, cursor, codex) support global scope only. When you omit both --global and --project-dir, the CLI defaults to global scope. Project-scoped harness installs (--project-dir without --global) are rejected for built-in harnesses.

Flags

The following table lists flags for jf agent plugins install.

During installation, the CLI verifies evidence when signing keys are configured in JFrog Artifactory.

Expected Output

When evidence verification fails:

10:14:10 [Warn] Evidence verification failed: <reason from server>
The plugin is unattested. Continue with installation? (y/n) [n]? y

When plugin files install successfully but the native agent CLI is missing from PATH (Claude or Codex harness only), the install summary reports a warning status with instructions to complete registration manually.

For path installs with a missing --version, the version picker matches Install a Skill (Select a version:).

CI Behavior

Evidence verification failure fails unless JFROG_PLUGINS_DISABLE_QUIET_FAILURE=true. See What to Set Explicitly for CI or Quiet Mode.

Examples

Install for Cursor using marketplace version:

jf agent plugins install my-plugin --harness cursor --repo agents-local

Install a specific version for multiple harnesses:

jf agent plugins install my-plugin --harness cursor,claude --repo agents-local --version 1.0.0

Install globally for Codex:

jf agent plugins install my-plugin --harness codex --repo agents-local --version latest

Install to a custom path:

jf agent plugins install my-plugin --path ./vendor/plugins --repo agents-local

Install Metadata

On successful install, the CLI writes .jfrog/plugin-info.json under each installed plugin directory. This manifest records the source repository, installed version, harness, scope, and project directory.

Post-Install Native Registration

For Claude and Codex harness installs, the CLI runs a post-install hook after copying plugin files:

1. Writes a local marketplace manifest under the harness marketplace root (for example, ~/.claude/plugins/local/jfrog/.claude-plugin/marketplace.json or ~/.agents/plugins/local/jfrog/.agents/plugins/marketplace.json).
2. If the native agent CLI is on PATH, registers the marketplace and installs the plugin with the agent CLI (claude plugin marketplace add, claude plugin install <slug>@<repo>, or the Codex equivalents).

If the native CLI is not installed, the file copy still succeeds and the install summary reports a warning status with instructions to complete registration manually. Cursor has no post-install hook; plugins are discovered from ~/.cursor/plugins/local/<slug>.

Each Artifactory repository gets an isolated marketplace subdirectory for Claude and Codex: plugin files land at <globalDir>/<REPO_KEY>/<slug> so installs from different repositories do not overwrite each other's marketplace registration.

Supported Built-in Harnesses

The following harnesses are supported out of the box for plugins. Paths are resolved from ~/.jfrog/agents/agent-config.json under the plugins-agents key. Built-in harnesses support global scope only.

<REPO_KEY> is the agent plugins repository key from --repo or auto-discovery.

To add or override a harness:

{
  "plugins-agents": {
    "my-agent": {
      "projectDir": ".my-agent/plugins",
      "globalDir": "~/.my-agent/plugins"
    }
  }
}

Custom harness entries may define both projectDir and globalDir. Project-scoped install is only available for harnesses with a non-empty projectDir.

You can also set plugin-manifest-paths in the same file to customize the ordered list of relative plugin.json paths checked during publish.

Delete a Plugin

Removes a specific version of a plugin from an agent plugins repository. The CLI does not show an interactive confirmation prompt or other terminal prompts. Repository auto-discovery behaves like other commands; see Plugins Repository Resolution.

To delete a plugin version from an agent plugins repository:

jf agent plugins delete PLUGIN_NAME --version PLUGIN_VERSION [--repo REPOSITORY_NAME]

Where:

• PLUGIN_NAME: Plugin slug to delete (CLI argument name: slug)
• PLUGIN_VERSION: Version to remove (required)
• REPOSITORY_NAME: Agent plugins repository key (optional when auto-discovered)

Flags

Examples

jf agent plugins delete my-plugin --version 1.0.0 --repo agents-local

Preview deletion:

jf agent plugins delete my-plugin --version 1.0.0 --repo agents-local --dry-run

Search Plugins

Searches for plugins by name across Agent Plugins repositories using the Artifactory property search API. The CLI matches against the agentplugins.name property. Use --repo to limit the search to one repository; when omitted, all local repositories with package type agentplugins are searched. This command has no interactive prompts; see Interactive and CI (non-interactive) modes.

To search for plugins by name:

jf agent plugins search QUERY [--repo REPOSITORY_NAME] [--format json]

Where:

• QUERY: Plugin name or search term (required positional argument)
• REPOSITORY_NAME: Optional repository to search (when omitted, searches all agentplugins repositories)

Flags

Examples

Search all agentplugins repositories:

jf agent plugins search web-scraper

Search a specific repository with JSON output:

jf agent plugins search web-scraper --repo agents-local --format json

Example JSON response:

[
  {
    "name": "web-scraper",
    "version": "1.2.0",
    "repository": "agents-local",
    "description": "Scrapes web pages for agent workflows."
  }
]

Plugins Repository Resolution

All jf agent plugins commands accept --repo to specify the target agent plugins repository. When --repo is omitted, the CLI resolves the repository using the following priority order:

1. --repo flag value
2. JFROG_AGENT_PLUGINS_REPO environment variable
3. Auto-discovery: queries JFrog Artifactory for all local repositories with package type agentplugins
   • If exactly one is found, it is used automatically.
   • If multiple are found in interactive mode, you are prompted to select one.
   • If multiple are found in CI or quiet mode, the command fails with the list of options.

Expected Output

When more than one agentplugins repository exists and --repo is omitted:

Select an agent plugins repository: agents-local

CI Behavior

Fails with: multiple agent plugins repositories found (repo-a, repo-b); specify --repo or set JFROG_AGENT_PLUGINS_REPO.

Plugins Environment Variables

Related Topics

• Agent Plugins Repositories
• JFrog CLI
• JFrog CLI Command Reference
• JFrog CLI for Skills
• Skills Repositories