microsoft/skills is a collection of skills, custom agents, AGENTS.md templates, plugins, hooks, commands, and MCP configurations that give AI coding agents context for Azure SDK and Microsoft AI Foundry development. Developers use it to install selected domain-specific guidance into coding-agent environments. The catalogue entries are the repository’s own agent resources and supporting configurations.
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 commands/microsoft/skills/deploygit clone --depth 1 https://github.com/microsoft/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/commands/microsoft/skills/deploy)<a href="https://agentmods.dev/commands/microsoft/skills/deploy"><img src="https://agentmods.dev/badge/commands/microsoft/skills/deploy.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.00018 | $0.01528 |
| Opus 5 | $0.00009 | $0.00764 |
| Sonnet 5 | $0.00004 | $0.00306 |
| Haiku 4.5 | $0.00002 | $0.00153 |
Grade A, and why
deploy 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 yesterday.
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 — 190 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Deep Wiki: Deploy to GitHub Pages
Generate a .github/workflows/deploy-wiki.yml GitHub Actions workflow that builds and deploys the VitePress wiki to GitHub Pages.
Step 1: Check Prerequisites
Before generating the workflow:
- Verify wiki exists: Check that
wiki/directory andwiki/package.jsonexist- If not, tell the user: "Run
/deep-wiki:buildfirst to scaffold the VitePress site."
- If not, tell the user: "Run
- Check for existing deployment workflows: Search for ANY existing GitHub Pages workflow:
# Check for exact file ls .github/workflows/deploy-wiki.yml 2>/dev/null # Check for any pages-related workflow grep -rl "deploy-pages\|pages-artifact\|github-pages" .github/workflows/ 2>/dev/null- If
deploy-wiki.ymlexists → STOP. Tell the user: "A deployment workflow already exists at.github/workflows/deploy-wiki.yml. No changes needed." - If a DIFFERENT pages workflow exists → ASK the user: "I found an existing GitHub Pages workflow at
{path}. Should I skip creating a new one, or createdeploy-wiki.ymlalongside it?" - If no pages workflow exists → proceed with generation
- If
Step 2: Generate Workflow File
Create .github/workflows/deploy-wiki.yml:
name: Deploy Wiki to GitHub Pages
on:
push:
branches: [main]
paths:
- 'wiki/**'
workflow_dispatch:
permissions:
contents: read
pages: write
id-token: write
concurrency:
group: pages
cancel-in-progress: false
jobs:
build:
runs-on: ubuntu-latest
steps:
- name: Checkout
uses: actions/checkout@v4
with:
fetch-depth: 0
- name: Setup Node
uses: actions/setup-node@v4
with:
node-version: 20
cache: npm
cache-dependency-path: wiki/package-lock.json
- name: Setup Pages
uses: actions/configure-pages@v5
- name: Install dependencies
run: npm ci
working-directory: wiki
- name: Build with VitePress
run: npm run build
working-directory: wiki
- name: Upload artifact
uses: actions/upload-pages-artifact@v3
with:
path: wiki/.vitepress/dist
deploy:
environment:
name: github-pages
url: ${{ steps.deployment.outputs.page_url }}
needs: build
runs-on: ubuntu-latest
steps:
- name: Deploy to GitHub Pages
id: deployment
uses: actions/deploy-pages@v4
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.
- yesterday First seen · 190 lines · 18 tokens per session scan A 8b799783312f
deploy is a command published in the GitHub repository microsoft/skills (2,992 stars, last pushed today), licensed MIT. It adds 18 tokens to every session and 1,528 once invoked, about $0.0001 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-09-03.
Other commands, from other repositories
workflow-automate
You are a workflow automation expert specializing in creating efficient CI/CD pipelines, GitHub Actions workflows, and automated development processes. Design and implement automation that reduces manual work, improves consistency, and accelerates delivery while maintaining quality and security.
setup-ci
Tu es un DevOps Engineer expert. Tu dois configurer un pipeline CI/CD adapté aux technologies du projet, en suivant les bonnes pratiques.
happy-start-cd.template
This prompt was authored for Claude-style slash workflows. In Codex runtime, adapt tool calls as follows.
check-pipeline
Analyze CI/CD pipeline configuration for optimization opportunities.
PAI
Status: Active | Last Updated: February 2026.
ci
Watch gh pr checks until green and fix failures on this branch. Do not merge.