A tool for changing Copilot Studio agent settings, instructions, and configuration files. Copilot Studio is Microsoft's platform for building conversational agents.

Use it to change an agent's name, instructions, conversation starters, AI settings, model configuration, or generative actions setting.

It helps you update an agent's behavior and visible details without manually searching through the project files. It also identifies the relevant file for each type of change.

edit-agent — Skill for Claude Code by microsoft

About the project

Skills for Copilot Studio is a plugin for authoring, testing, and troubleshooting standard Microsoft Copilot Studio agents as YAML files from a terminal or editor. It is intended for users of Claude Code, GitHub Copilot CLI, and VS Code who work with Copilot Studio agents. The catalogue add-ons are the plugin's skills, agents, hook, and plugin definition.

microsoft/skills-for-copilot-studio · 430 stars · on GitHub

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent

npx skills add microsoft/skills-for-copilot-studio --skill edit-agent

Clone the repo

git clone --depth 1 https://github.com/microsoft/skills-for-copilot-studio

Made for: Claude Code.

Or install copilot-studio, the plugin that ships this one along with the rest of its 31 skills, 4 agents, 1 hook.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/microsoft/skills-for-copilot-studio/edit-agent.svg)](https://agentmods.dev/skills/microsoft/skills-for-copilot-studio/edit-agent)

Your own site

<a href="https://agentmods.dev/skills/microsoft/skills-for-copilot-studio/edit-agent"><img src="https://agentmods.dev/badge/skills/microsoft/skills-for-copilot-studio/edit-agent.svg" alt="Measured on agentmods" height="20"></a>

Per session 37 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 776 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00037	$0.00776
Opus 5	$0.00018	$0.00388
Sonnet 5	$0.00007	$0.00155
Haiku 4.5	$0.00004	$0.00078

Measured 7d ago against content hash b17b42205c86, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

edit-agent scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 7d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/edit-agent/SKILL.md · 82 lines

How it starts

The opening of the file, as written. The whole thing — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Edit Agent Settings/Instructions

Modify agent metadata (agent.mcs.yml) or configuration (settings.mcs.yml).

Instructions

Auto-discover the agent directory:
```
Glob: **/agent.mcs.yml
```
NEVER hardcode an agent name. If multiple agents found, ask which one.
Identify what the user wants to change and read the appropriate file:
- Instructions, display name, conversation starters, AI settings → agent.mcs.yml
- GenerativeActionsEnabled, authentication, recognizer, capabilities → settings.mcs.yml
If the user wants to change the AI model, run the schema lookup tool first:
```
node ${CLAUDE_SKILL_DIR}/../../scripts/schema-lookup.bundle.js models
```
Use the output to determine the correct modelNameHint and provider values. CRITICAL: Do NOT include kind in the model block — the agent-level schema uses CurrentModelsNoKind.
Read the current file before making any changes.
Make the requested changes using the Edit tool.

Editable Fields in `agent.mcs.yml`

Field	Description	Example
`displayName`	Agent's display name	`displayName: My Agent`
`instructions`	System prompt / personality	Multi-line YAML with `\|`
`conversationStarters`	Suggested conversation starters	Array of `{title, text}`
`aISettings.model.modelNameHint`	Model hint (run `models` command for convention)	`Sonnet46`, `GPT5Chat`
`aISettings.model.provider`	Model provider (required for non-OpenAI)	`Anthropic`

Editable Fields in `settings.mcs.yml`

Field	Description	Example
`GenerativeActionsEnabled`	Enable generative orchestration	`true` / `false`
`authenticationMode`	Auth mode	`Integrated`, `None`
`authenticationTrigger`	When to auth	`Always`, `AsNeeded`
`accessControlPolicy`	Access control	`ChatbotReaders`
`configuration.aISettings.*`	AI capabilities	Various booleans
`configuration.settings.*.content.capabilities.webBrowsing`	Web browsing	`true` / `false`

Read the full file on GitHub · 82 lines

Files

What ships with it

1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

instructions-guide.md 2.7 KB

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

7d ago First seen · 82 lines · 37 tokens per session scan A b17b42205c86

Subscribe to this mod's changes

edit-agent is a skill published in the GitHub repository microsoft/skills-for-copilot-studio (430 stars, last pushed 3d ago), licensed MIT. It adds 37 tokens to every session and 776 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Building agents

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens