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/askgit 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/ask)<a href="https://agentmods.dev/commands/microsoft/skills/ask"><img src="https://agentmods.dev/badge/commands/microsoft/skills/ask.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.00013 | $0.00482 |
| Opus 5 | $0.00006 | $0.00241 |
| Sonnet 5 | $0.00003 | $0.00096 |
| Haiku 4.5 | $0.00001 | $0.00048 |
Grade A, and why
ask 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.
What it actually says
Deep Wiki: Repository Q&A
Answer a question about this repository grounded in actual source code.
Source Repository Resolution (MUST DO FIRST)
Before answering, resolve the source repository context:
- Check for git remote: Run
git remote get-url origin - Ask the user: "Is this a local-only repository, or do you have a source repository URL?"
- Remote URL → store as
REPO_URL, use linked citations:[file:line](REPO_URL/blob/BRANCH/file#Lline) - Local → use
(file_path:line_number)
- Remote URL → store as
- Determine default branch: Run
git rev-parse --abbrev-ref HEAD - Do NOT proceed until resolved
Question
$ARGUMENTS
Process
- Detect language of the question and respond in the same language
- Search the codebase for files relevant to the question
- Read those files to gather evidence
- Synthesize an answer grounded entirely in actual code — never invent or guess
Response Format
## [Concise Answer Title]
[1-2 paragraph direct answer]
### How It Works
[Detailed explanation with inline code citations and at least 1 Mermaid diagram when the answer involves architecture, flow, or relationships]
### Key Files
| File | Purpose | Source |
|------|---------|--------|
| `src/path/file.ts` | [Role in the system] | [linked citation] |
### Code Example
<!-- Source: file_path:line_number -->
[Relevant snippet from actual source, if helpful]
### Related
- [Related concepts or files to explore]
Rules
- ONLY use information from actual source files in this repository
- NEVER invent, guess, or use external knowledge
- ALWAYS cite source files inline using the resolved citation format:
- Remote:
[src/path/file.ts:42](REPO_URL/blob/BRANCH/src/path/file.ts#L42) - Local:
(src/path/file.ts:42)
- Remote:
- Think step by step through complex questions
- If information is insufficient, say so explicitly and suggest which files to examine
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 · 63 lines · 13 tokens per session scan A 1a95373a9984
ask is a command published in the GitHub repository microsoft/skills (2,989 stars, last pushed yesterday), licensed MIT. It adds 13 tokens to every session and 482 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
OPSX: Apply
Implement tasks from an OpenSpec change (Experimental).
debug
You are acting as a Debug Specialist with expertise in.
audit-security
Perform comprehensive security audit of the current project.
add-database-railway
Set up PostgreSQL database with Prisma ORM and complete data layer.
setup-monitoring-railway
Configure comprehensive monitoring for Railway deployment.
review-security
Perform comprehensive security audit using code-review-agent and security-production-agent. Scan for OWASP Top 10 vulnerabilities: SQL injection, XSS, CSRF, insecure authentication, broken access control, security misconfiguration, sensitive data exposure, insufficient logging, insecure deserialization, and vulnerable…