Plugin scope now authors a single vendor-neutral .apm/agents/<name>.agent.md file (name/description/model/body only) instead of a Claude Code + Copilot CLI pair, per ADR-0016: apm compile has no per-target field integrator, so tools: and all Claude-only fields (isolation/maxTurns/effort/memory/ permissionMode) are omitted entirely rather than shipping a value that's guaranteed wrong on one harness. Scope detection switches from a flat plugin.json check to the same apm.yml+type: walk-up agent-audit's validate.sh already uses. Project scope and user scope are unaffected — both keep the existing dual-file pair model. Refs: #89
987 B
987 B
assets/
templates/
Annotated agent definition templates copied by scripts/new-agent.sh when scaffolding a new agent.
claude-code.md— Claude Code agent definition template (project/user scope). Includes all supported frontmatter fields (required and optional) with inline guidance comments andFILL IN:placeholders.copilot.agent.md— Copilot CLI agent definition template (CLI format, project/user scope). Excludes cloud/IDE-only fields (target,user-invocable,disable-model-invocation,mcp-servers) and Claude Code-only fields. Uses Copilot tool aliases (execute,read,edit,search,agent,web).apm-agent.md— Vendor-neutral APM agent definition template (plugin/APM scope). Onlyname,description, and optionalmodelin frontmatter — notoolsand no Claude-only fields, sinceapm compilecopies frontmatter verbatim to both the Claude Code and Copilot CLI targets with no per-target integrator (ADR-0016).