Agent Examples¶

Ten example agents for VS Code live as real files in agents/ in the repository. The files are the single source, so this page does not reproduce them. The Agents overview lists each one.

Every example uses only properties VS Code reads, leaves model unset so it follows your model picker, and uses portable tool aliases.

Install¶

gh copilot agent install CowboyLogic/ai-dev/agents/code-reviewer.agent.md

Or copy the .agent.md file into .github/agents/ in your workspace, or into ~/.copilot/agents/ for every workspace. Agents that name other agents in agents: need those agents installed too.

What each group demonstrates¶

Group	Agents	Shows
Read-only reviewers	`code-reviewer`, `security-auditor`, `performance-reviewer`	Limiting `tools` to `read` and `search` so the agent cannot change anything
Builders	`test-engineer`, `react-developer`, `docs-writer`, `api-designer`	Granting `edit` and `execute` only where the job needs them
Coordinators	`architecture-coordinator`, `feature-lead`, `review-coordinator`	The `agents` property and the `agent` tool, delegating to the specialists above
Handoff	`code-reviewer`	A `handoffs` entry that sends the findings to `test-engineer`

The coordinators call these agents by name, so install them together:

Coordinator	Needs
`architecture-coordinator`	`api-designer`, `security-auditor`, `performance-reviewer`
`feature-lead`	`api-designer`, `react-developer`, `test-engineer`, `code-reviewer`, `docs-writer`
`review-coordinator`	`code-reviewer`, `security-auditor`, `performance-reviewer`

Adapt one¶

Copy the closest example.
Rewrite the description for your task. Other agents read it to decide whether to call this one.
Trim tools to what the job needs.
Replace the generic guidance in the body with your project's conventions.

See Custom Agent Files for the format, and Best Practices for design guidance.