agentleFS
MicrosoftKnown publishermicrosoft/vscode-copilot-chat/assets/prompts/skills/agent-customization/references/agents.md

vscode-copilot-chat / references

AGENTS.md10k starsChanged 7 months agoMITArchived repositoryView on GitHub

Custom personas with specific tools, instructions, and behaviors. Use for orchestrated workflows with role-based tool restrictions. Sources: built-in aliases, specific tools, MCP servers (<server>/*), extension tools. Special: [] = no tools, omit = defaults. Body reference: #tool:<name> To discover available tools, check your current tool list or use #tool: syntax in the body to reference specific tools.

We split this agents.md into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Minimal tools: Only include what the role needs—excess tools dilute focus

    line 102

≈ “Common” is an estimate: at least 1 in 5 of the 36,368 AGENTS.md files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
agents.md

Custom Agents (.agent.md)

Custom personas with specific tools, instructions, and behaviors. Use for orchestrated workflows with role-based tool restrictions.

Locations

PathScope
.github/agents/*.agent.mdWorkspace
<profile>/agents/*.agent.mdUser profile

Frontmatter

---
description: "<required>"    # For agent picker and subagent discovery
name: "Agent Name"           # Optional, defaults to filename
tools: [search, web]         # Optional: aliases, MCP (<server>/*), extension tools
model: "Claude Sonnet 4"     # Optional, uses picker default; supports array for fallback
argument-hint: "Task..."     # Optional, input guidance
agents: [agent1, agent2]     # Optional, restrict allowed subagents by name (omit = all, [] = none)
user-invocable: true         # Optional, show in agent picker (default: true)
disable-model-invocation: false  # Optional, prevent subagent invocation (default: false)
handoffs: [...]              # Optional, transitions to other agents
---

Invocation Control

AttributeDefaultEffect
user-invocable: falsetrueHide from agent picker, only accessible as subagent
disable-model-invocation: truefalsePrevent other agents from invoking as subagent

Model Fallback

model: ['Claude Sonnet 4.5 (copilot)', 'GPT-5 (copilot)']  # First available model is used

Tools

Sources: built-in aliases, specific tools, MCP servers (<server>/*), extension tools.

Special: [] = no tools, omit = defaults. Body reference: #tool:<name>

Tool Aliases

AliasPurpose
executeRun shell commands
readRead file contents
editEdit files
searchSearch files or text
agentInvoke custom agents as subagents
webFetch URLs and web search
todoManage task lists

Common Patterns

tools: [read, search]             # Read-only research
tools: [myserver/*]               # MCP server only
tools: [read, edit, search]       # No terminal access
tools: []                         # Conversational only

To discover available tools, check your current tool list or use #tool: syntax in the body to reference specific tools.

Template

---
description: "{Use when... trigger phrases for subagent discovery}"
tools: [{minimal set of tool aliases}]
user-invocable: false
---
You are a specialist at {specific task}. Your job is to {clear purpose}.

## Constraints
- DO NOT {thing this agent should never do}
- DO NOT {another restriction}
- ONLY {the one thing this agent does}

## Approach
1. {Step one of how this agent works}
2. {Step two}
3. {Step three}

## Output Format
{Exactly what this agent should return}

Invocation

  • Manual: Agent selector in chat
  • Subagent: Parent agent delegates based on description match (when infer allows)

Core Principles

  1. Single role: One persona with focused responsibilities per agent
  2. Minimal tools: Only include what the role needs—excess tools dilute focus
  3. Clear boundaries: Define what the agent should NOT do
  4. Keyword-rich description: Include trigger words so parent agents know when to delegate

Anti-patterns

  • Swiss-army agents: Too many tools, tries to do everything
  • Vague descriptions: "A helpful agent" doesn't guide delegation—be specific
  • Role confusion: Description doesn't match body persona
  • Circular handoffs: A → B → A without progress criteria

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.