Microsoft Agent 365 Skills is a collection of coding-agent skills and MCP configuration for building and operating AI Teammates hosted in Microsoft Teams. It supports the Agent 365 lifecycle, including WorkIQ integration, registration, observability, validation, and local testing, for users of Claude Code and GitHub Copilot.
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 skills/microsoft/agent365-skills/a365-setupnpx skills add microsoft/agent365-skills --skill a365-setupgit clone --depth 1 https://github.com/microsoft/agent365-skillsWrote 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/skills/microsoft/agent365-skills/a365-setup)<a href="https://agentmods.dev/skills/microsoft/agent365-skills/a365-setup"><img src="https://agentmods.dev/badge/skills/microsoft/agent365-skills/a365-setup.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.00125 | $0.11036 |
| Opus 5 | $0.00063 | $0.05518 |
| Sonnet 5 | $0.00025 | $0.02207 |
| Haiku 4.5 | $0.00013 | $0.01104 |
Grade D, and why
a365-setup scanned grade D with 3 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
> - **Linux:** `curl -sL https://aka.ms/InstallAzureCLIDeb | sudo bash` Downloads and executes remote codehighSupply chain
curl | sh runs whatever the server returns today, which is not necessarily what it returned when this was reviewed.
> - **Linux:** `curl -sL https://aka.ms/InstallAzureCLIDeb | sudo bash` Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
> - **Linux:** `curl -sL https://aka.ms/InstallAzureCLIDeb | sudo bash` How it starts
The opening of the file, as written. The whole thing — 836 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent 365 CLI Setup
Trigger phrases — any of these will activate this skill automatically:
- "set up agent 365 for this agent"
- "run a365 setup"
- "onboard this agent to agent 365"
- "register this agent with agent 365"
- "provision this agent with agent 365"
- "add agent 365 to this agent"
- "connect this agent to agent 365"
- "make this agent an a365 agent"
- "make this agent discoverable in Agent 365"
- "create a365 blueprint"
- "start agent 365 setup"
YOUR VERY FIRST ACTION: Output the intro message below to the user, then silently detect the agent stack. Do NOT create todos, run setup commands, or read further until all Phase 1 questions are answered.
MANDATORY INTRO MESSAGE — output this before doing anything else:
I'll help you set up Agent 365 for this agent. Here's what I'll do:
1. Detect your agent type, stack, and language (silently, takes a few seconds)
2. Ask you to confirm what I found — or correct anything I got wrong
3. Ask how your agent authenticates (OBO / S2S)
4. Ask which capabilities you want (Register, Observability, WorkIQ, AI Teammate)
After those answers, I'll install any missing prerequisites, validate your Azure
environment, and hand off to the right skill for the rest of setup.
Detecting your agent now…
RULE 1 — DETECT AGENT STACK AND CODE, ASK VALIDATION QUESTIONS, THEN CREATE ALL TODOS.
Phase 1A: Silent Detection
First: Check for detection cache. Read .a365-workspace-detection.local.json if it exists. If detectedAt is within the last 60 minutes, load agentStack, programmingLanguage, and usesTeamsOrCopilot from it and skip the detection steps below — go straight to Phase 1B.
Run all three detection steps in parallel (single tool call with multiple Glob/Grep):
Step 1: Detect Agent Stack → Store as agentStack
- Check for .csproj + Microsoft.Agents.* →
Agent Framework - Check for package.json + @langchain →
LangChain - Check for package.json + "openai" (no LangChain) →
OpenAI - Check for requirements.txt + langchain →
LangChain - Check for requirements.txt + openai →
OpenAI
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 · 836 lines · 125 tokens per session scan D 3cfe473fffb8
a365-setup is a skill published in the GitHub repository microsoft/agent365-skills (34 stars, last pushed 9d ago), licensed MIT. It adds 125 tokens to every session and 11,036 once invoked, about $0.0006 per session on Opus 5. A static security scan graded it D with 3 findings (asks for root, downloads and executes remote code, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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.
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…