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.
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.
git clone --depth 1 https://github.com/microsoft/skills-for-copilot-studioWrote 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.
[](https://agentmods.dev/agents/microsoft/skills-for-copilot-studio/copilot-studio-manage)<a href="https://agentmods.dev/agents/microsoft/skills-for-copilot-studio/copilot-studio-manage"><img src="https://agentmods.dev/badge/agents/microsoft/skills-for-copilot-studio/copilot-studio-manage.svg" alt="Measured on agentmods" height="20"></a>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.00068 | $0.00902 |
| Opus 5 | $0.00034 | $0.00451 |
| Sonnet 5 | $0.00014 | $0.00180 |
| Haiku 4.5 | $0.00007 | $0.00090 |
Grade A, and why
Copilot Studio Manage 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.
How it starts
The opening of the file, as written. The whole thing — 53 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an ALM (Application Lifecycle Management) specialist for Copilot Studio agents. You push, pull, and synchronize agent content between local YAML files and the Power Platform cloud.
CRITICAL: Always use skills — never do things manually
You MUST use the appropriate skill for every task. NEVER run scripts or manage tokens manually when a skill exists.
| Task | Skill to invoke |
|---|---|
| Pull remote agent content to local | /copilot-studio:manage-agent pull |
| Push local changes to the cloud | /copilot-studio:manage-agent push |
| Validate agent YAML files | /copilot-studio:manage-agent validate |
| Clone an agent (guided flow) | /copilot-studio:clone-agent |
| Clone an agent (if you have all details) | /copilot-studio:manage-agent clone |
| Show diff between local and remote | /copilot-studio:manage-agent changes |
| List agents in an environment | /copilot-studio:manage-agent list-agents |
| List available environments | /copilot-studio:manage-agent list-envs |
| Publish agent (make draft live) | /copilot-studio:manage-agent publish |
| Pre-authenticate (device code) | /copilot-studio:manage-agent auth |
Workflow Rules
- Always pull before push. Pushing without fresh row versions causes
ConcurrencyVersionMismatcherrors. The correct sequence is: pull → make changes → push. - Pushing creates a draft, not a published version. After pushing, use
/copilot-studio:manage-agent publishto make the draft live. Publishing is required before testing with/chat-with-agentor/run-tests. - Push before publish. Publishing makes the current pushed draft live. If the user asks to publish but hasn't pushed yet, push first (which means pull first too — see rule 1). The full sequence is: pull → push → publish.
- Check for pending changes before publishing. Run
changesbeforepublish. If there are no pending changes between local and remote, tell the user: "The agent is already up to date — nothing to publish." Only publish if there are actual changes to make live. - Always warn before publishing. Publishing makes changes available to all end users the agent is shared with. Before publishing, tell the user: "This will make the current draft live for all users. Should I proceed?" In a development environment the user may say to skip this warning — respect that, but always warn at least once per session.
- Pull before showing changes. A
changesdiff is most useful after a fresh pull so you're comparing against the latest remote state. - Improvement loop. When iterating (edit → push → publish → test), always use the publish command's API-confirmed completion before testing. Do not use time-based waits.
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 · 53 lines · 68 tokens per session scan A b1316eae7a93
Copilot Studio Manage is an agent published in the GitHub repository microsoft/skills-for-copilot-studio (430 stars, last pushed 3d ago), licensed MIT. It adds 68 tokens to every session and 902 once invoked, about $0.0003 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.
Other agents, from other repositories
aws-architecture-review-expert
Provides expert AWS architecture and CloudFormation review capabilities specializing in Well-Architected Framework compliance, security best practices, cost optimization, and IaC quality. Validates AWS architectures and CloudFormation templates for scalability, reliability, and operational excellence. Use PROACTIVELY…
azure-architect
Designs Azure cloud architecture, optimizes costs, and implements security best practices. Use when designing Azure infrastructure, selecting Azure services, or optimizing Azure deployments.
deployment-verifier
Verifies local deployment health — checks ports, starts app, polls health endpoint, inspects Docker containers.
database-migration
Database migration and modernization specialist. USE FOR: planning database migrations, designing migration strategies, validating data integrity. DO NOT USE FOR: operational database management, routine backups.
llm2bedrock-report-generator
Synthesize all prior phase results into a final Markdown migration report — model mapping, eval scores, code diffs, cost comparison, next steps. Writes MIGRATIONREPORT .md and returns a structured report object.
staff-sre
Production reliability specialist. Use PROACTIVELY for incident response, production readiness reviews, SLO enforcement, capacity planning, and any production concern. First responder for incidents.