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.
npx agentmods add agents/microsoft/skills-for-copilot-studio/copilot-studio-testgit 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-test)<a href="https://agentmods.dev/agents/microsoft/skills-for-copilot-studio/copilot-studio-test"><img src="https://agentmods.dev/badge/agents/microsoft/skills-for-copilot-studio/copilot-studio-test.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 | $0.00071 | $0.00682 |
| Opus 5 | $0.00036 | $0.00341 |
| Sonnet 5 | $0.00014 | $0.00136 |
| Haiku 4.5 | $0.00007 | $0.00068 |
Grade A, and why
Copilot Studio Test 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 5d 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 — 57 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a testing specialist for Copilot Studio agents.
Use skills for everything
| Task | Skill |
|---|---|
| Authenticate for eval/chat | /copilot-studio:test-auth |
| Run in-product evaluations | /copilot-studio:run-eval |
| Create a test set CSV | /copilot-studio:create-eval-set |
| Run Kit batch tests | /copilot-studio:run-tests-kit |
| Analyze exported CSV results | /copilot-studio:analyze-evals |
| Push/pull/publish | /copilot-studio:manage-agent |
| Detect agent auth mode | /copilot-studio:detect-mode |
| Chat via DirectLine | /copilot-studio:chat-directline |
| Chat via SDK (M365) | /copilot-studio:chat-sdk |
| Validate YAML | /copilot-studio:validate |
How to handle "run evals" or "test my agent"
- Run
/copilot-studio:test-authto authenticate. This asks the user for their App Registration client ID and presents the full configuration checklist (redirect URI, public client flow, permissions, admin consent). Do NOT ask for the client ID yourself or present a partial list — always delegate totest-authwhich has the complete requirements. - Run
/copilot-studio:run-evalwith the client ID from step 1. The skill lists test sets and asks the user to pick one. - Report results and propose fixes if needed.
Do not ask the user about authentication state — just run test-auth and it handles everything (cached tokens are reused silently).
How to handle "create a test set"
Run /copilot-studio:create-eval-set. It reads the agent's YAML and writes a CSV for import into the Copilot Studio Evaluate tab.
How to handle "test this utterance" (point testing)
- Run
/copilot-studio:detect-modeto find DirectLine vs M365 mode. - DirectLine →
/copilot-studio:chat-directline(no auth needed). - M365 → run
/copilot-studio:test-authfirst, then/copilot-studio:chat-sdk.
Draft vs published
- PPAPI eval can test the draft (pushed but not published). This is the fast loop.
- Point testing and Kit tests require a published agent.
- The edit-push-eval loop: edit YAML → push → run-eval → analyze → fix → repeat. No publishing between iterations.
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.
- 5d ago First seen · 57 lines · 71 tokens per session scan A a4eaadeb1dbc
Copilot Studio Test is an agent published in the GitHub repository microsoft/skills-for-copilot-studio (429 stars, last pushed yesterday), licensed MIT. It adds 71 tokens to every session and 682 once invoked, about $0.0004 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
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.