Copilot New Agent.prompt

---
description: Scaffold a new custom agent (.agent.md) for VS Code and/or GitHub Copilot
name: New Custom Agent
agent: Copilot Customization Builder
tools: ['search', 'edit/editFiles']
---

# New Custom Agent

Create a new custom agent profile in this repository.

## Inputs

- Agent file slug (filename, without `.agent.md`): `${input:agentSlug}`
- Agent display name: `${input:agentName}`
- One-line description: `${input:agentDescription}`
- Target environment (`vscode`, `github-copilot`, or `both`): `${input:agentTarget}`
- Tools list (comma-separated, or leave blank to propose a minimal set): `${input:agentTools}`

## Requirements

1. Inspect existing agents in `.github/agents/` and match conventions (YAML keys, quoting style).
2. Create the agent file at: `.github/agents/${input:agentSlug}.agent.md`
3. In YAML frontmatter, use these fields:
   - `description` (required): Brief description shown as placeholder text in chat input
   - `name` (recommended): Display name (defaults to filename if omitted)
   - `tools` (recommended): Explicit list of available tools (prefer minimal)
       - Can include built-in tools, tool aliases, extension tools, tool sets, or MCP tools (`<server>/<tool>`, `<server>/*`)
   - `target`: Set to `vscode` or `github-copilot` if restricting; omit for both
   - `model` (optional): Specific AI model or prioritized array of models
   - `user-invocable` (optional): Boolean to control agents dropdown visibility (default: true)
   - `disable-model-invocation` (optional): Boolean to prevent subagent invocation (default: false)
   - `argument-hint` (optional): Hint text shown in chat input field
   - `handoffs` (optional): List of suggested next actions to transition between agents
   - `hooks` (optional, preview): Lifecycle hooks scoped to this agent
   - `mcp-servers` (optional): MCP server configs for GitHub Copilot target
4. In the Markdown body, include:
   - What the agent does
   - A default workflow (how it operates)
   - Guardrails (safety + scope boundaries)
   - Use `#tool:<tool-name>` syntax to reference tools in body text
5. Don't add repo-specific behavior unless requested.

## Handoffs (optional)

If creating a workflow agent, consider adding handoffs: