microsoft/Build26-BRK242-turn-your-agents-into-action-connect-tools-apis-and-documents contains Microsoft Build 2026 session resources about connecting AI agents to tools, APIs, and documents through governed tool selection. It is intended for developers building agents that need efficient access to MCP servers, A2A, OpenAPI, connectors, built-in tools, and structured content from multimodal files. The catalogue add-ons are session instructions for exploring these agent-building patterns.
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 skills add microsoft/Build26-BRK242-turn-your-agents-into-action-connect-tools-apis-and-documents --skill work-order-managementgit clone --depth 1 https://github.com/microsoft/Build26-BRK242-turn-your-agents-into-action-connect-tools-apis-and-documentsWrote 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/build26-brk242-turn-your-agents-into-action-connect-tools-apis-and-documents/work-order-management)<a href="https://agentmods.dev/skills/microsoft/build26-brk242-turn-your-agents-into-action-connect-tools-apis-and-documents/work-order-management"><img src="https://agentmods.dev/badge/skills/microsoft/build26-brk242-turn-your-agents-into-action-connect-tools-apis-and-documents/work-order-management/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/microsoft/build26-brk242-turn-your-agents-into-action-connect-tools-apis-and-documents/work-order-management"><img src="https://agentmods.dev/badge/skills/microsoft/build26-brk242-turn-your-agents-into-action-connect-tools-apis-and-documents/work-order-management.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00045 | $0.01221 |
| Opus 5 | $0.00023 | $0.00611 |
| Sonnet 5 | $0.00009 | $0.00244 |
| Haiku 4.5 | $0.00005 | $0.00122 |
Grade A, and why
work-order-management 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 12d 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 — 121 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Work Order Management
Use this skill for any work order operation — viewing, listing, creating, or updating.
When to Use
- "Show me WO-007"
- "What are my open work orders?"
- "Create a work order for fiber splice at 123 Main St"
- "Mark WO-003 as completed"
- "What critical work orders are pending?"
- "Assign WO-010 to Sarah"
Tools Used by This Skill
All work order capabilities live in the Foundry Toolbox under the work_orders MCP server, so the actual tool names are prefixed work_orders___.
| Capability | Prefixed tool name |
|---|---|
| List / filter work orders | work_orders___list_work_orders_work_orders_get |
| Get a specific work order | work_orders___get_work_order_work_orders__work_order_id__get |
| Create a work order | work_orders___create_work_order_work_orders_post |
| Update a work order | work_orders___update_work_order_work_orders__work_order_id__patch |
Step 0: Discover tools (REQUIRED before first work-order call this turn)
If the work-order tools aren't already visible in your tool list, call tool_search once with limit: 10 and a short query like "work order". Examples:
tool_search({"query": "work order", "limit": 10})tool_search({"query": "create work order", "limit": 10})for create flows
The returned tools stay callable for the rest of the turn — do not search again.
Step 1: Choose the Right Operation
| Request Type | Tool (prefixed name) | Key Parameters |
|---|---|---|
| View a specific WO | work_orders___get_work_order_* |
work_order_id (e.g. WO-007) |
| List / filter WOs | work_orders___list_work_orders_* |
status, priority, assigned_technician |
| Create a new WO | work_orders___create_work_order_* |
title, description, priority, technician, location, due_date |
| Update an existing WO | work_orders___update_work_order_* |
work_order_id + fields to change |
Invoke each tool via call_tool with {"name": "<prefixed_name>", "arguments": {...}}.
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.
- 12d ago First seen · 121 lines · 45 tokens per session scan A ebab97a5e04d
work-order-management is a skill published in the GitHub repository microsoft/Build26-BRK242-turn-your-agents-into-action-connect-tools-apis-and-documents (10 stars, last pushed 23d ago), licensed MIT. It adds 45 tokens to every session and 1,221 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-08-31.
Other skills, from other repositories
github-integration
A coding aid for working with GitHub, a service for hosting code and coordinating software work. It supports creating and querying issues and pull requests and retrieving repository information.
teams-dev
Use this skill whenever the user mentions Microsoft Teams in a development context — whether they're building, integrating, configuring, debugging, or just asking questions. Covers bots, message extensions, embedded web apps, Adaptive Cards, dialogs, SSO, infrastructure, the Teams Developer CLI/SDK, and general Teams…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
magpie-security-issue-import-from-md
Open one or more tracking issues from a markdown file containing a batch of security findings. Each finding becomes one tracker landing in the Needs triage board column. The file itself is the full report — there is no inbound reporter to reply to and no PR to inspect.
remove
Remove a deployed framework or addon from the current workspace.