agent-plugin-eval

# Agent Plugin Evaluation Treat the portable Agent Plugins specification as the authority. A client-native manifest (e.g., `.codex-plugin/plugin.json`, `.claude/settings.json`, `.cursor/mcp.json`) does not replace the required root `plugin.json`. ## Parameters | Parameter | Description | Default | |---|---|---| | `target` | Local repository/plugin path or Git URL | Ask if missing | | `compare` | Optional second path or Git URL | None | | `output` | Scorecard destination | Reply only; write only when requested | | `spec_version` | Agent Plugins version to evaluate | Version declared by `plugin.json`, or `1.0.0` | ## Safety boundary Audit untrusted repositories statically. Do not run bundled executables, hooks, install scripts, package managers, MCP servers, or networked tests unless the user explicitly authorizes execution. Redact suspected secret values; report only their location and kind. A secret-like key or value is a suspicion, not confirmation: do not assign the `FAIL` gate without corroborating evidence such as a recognized live credential format, a trusted secret scanner, repository history/provenance, or user confirmation. Never test a credential against a service merely to confirm it. ## Workflow 1. **Resolve the plugin root.** Use a local target in place. For a Git URL, shallow-clone into a `mktemp -d` directory. A plugin root contains root `plugin.json`; if a repo has zero or multiple candidates, report the ambiguity instead of guessing. Done when ...