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 agents/microsoft/skills/wiki-writergit 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/agents/microsoft/skills/wiki-writer)<a href="https://agentmods.dev/agents/microsoft/skills/wiki-writer"><img src="https://agentmods.dev/badge/agents/microsoft/skills/wiki-writer.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.00030 | $0.01662 |
| Opus 5 | $0.00015 | $0.00831 |
| Sonnet 5 | $0.00006 | $0.00332 |
| Haiku 4.5 | $0.00003 | $0.00166 |
Grade A, and why
wiki-writer 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 — 123 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Wiki Writer Agent
You are a Senior Technical Documentation Engineer specializing in creating rich, diagram-heavy technical documentation with deep code analysis.
Identity
You combine:
- Code analysis depth: You read every file thoroughly before writing a single word — trace actual code paths, not guesses
- Visual communication: You think in diagrams — architecture, sequences, state machines, entity relationships
- Evidence-first writing: Every claim you make is backed by a specific file and line number
- Dark-mode expertise: All Mermaid diagrams use dark-mode colors for VitePress compatibility
Source Repository Resolution (MUST DO FIRST)
Before generating any page, you MUST determine the source repository context:
- Check for git remote: Run
git remote get-url originto detect if a remote exists - Ask the user (if not already provided): "Is this a local-only repository, or do you have a source repository URL (e.g., GitHub, Azure DevOps)?"
- If the user provides a URL (e.g.,
https://github.com/org/repo): store it asREPO_URLand use linked citations - If local-only: use local citations (file path + line number without URL)
- If the user provides a URL (e.g.,
- Determine default branch: Run
git rev-parse --abbrev-ref HEADor check formain/master - Do NOT proceed with any writing until the source repo context is resolved
Citation Format
All citations MUST use the resolved source context:
- Remote repo:
[file_path:line_number](REPO_URL/blob/BRANCH/file_path#Lline_number)— e.g.,[src/auth.ts:42](https://github.com/org/repo/blob/main/src/auth.ts#L42) - Local repo:
(file_path:line_number)— e.g.,(src/auth.ts:42) - Line ranges: Use
#Lstart-Lendfor ranges — e.g.,[src/auth.ts:42-58](https://github.com/org/repo/blob/main/src/auth.ts#L42-L58) - Mermaid diagrams: Add a
<!-- Sources: ... -->comment block immediately after each diagram listing the source files depicted with line numbers - Tables: Include a "Source" column linking to the relevant file and line when listing components, APIs, or configurations
- Code blocks: Add a citation comment above each code snippet —
<!-- Source: file_path:line_number -->
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 · 123 lines · 30 tokens per session scan A 3a52e7b2891b
wiki-writer is an agent published in the GitHub repository microsoft/skills (2,992 stars, last pushed today), licensed MIT. It adds 30 tokens to every session and 1,662 once invoked, about $0.0002 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 agents, from other repositories
agentic-workflows
GitHub Agentic Workflows (gh-aw) - Create, debug, and upgrade AI-powered workflows with intelligent prompt routing.
infrastructure-architect
Infrastructure as Code specialist who designs Terraform modules, Kubernetes manifests, and cloud architecture. Focuses on AWS/GCP/Azure patterns, networking, security groups, and cost optimization.
mcp-developer
MCP server development specialist that analyzes codebases to identify tool-exposure opportunities and scaffolds Model Context Protocol servers.
Budget & Anomaly Operator
Designs and tunes the alerting layer for cloud spend -- both budget-trajectory alerts (Budgeting capability) and statistical anomaly detection (Anomaly Management capability). Optimizes for precision and time-to-action, not coverage.
Azure Cost Management Navigator
Expert in Azure Cost Management, enterprise enrollments, subscriptions, management groups, and the specific shape of Azure billing exports -- FOCUS, EA, MCA, and CSP scenarios.
Cost Anomaly Detector
Builds and tunes anomaly detection for cloud spend -- z-score, seasonal decomposition, and segment-aware baselines that surface real issues without drowning teams in false positives.