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-preparationgit 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-preparation)<a href="https://agentmods.dev/skills/microsoft/build26-brk242-turn-your-agents-into-action-connect-tools-apis-and-documents/work-order-preparation"><img src="https://agentmods.dev/badge/skills/microsoft/build26-brk242-turn-your-agents-into-action-connect-tools-apis-and-documents/work-order-preparation/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-preparation"><img src="https://agentmods.dev/badge/skills/microsoft/build26-brk242-turn-your-agents-into-action-connect-tools-apis-and-documents/work-order-preparation.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.00057 | $0.00974 |
| Opus 5 | $0.00028 | $0.00487 |
| Sonnet 5 | $0.00011 | $0.00195 |
| Haiku 4.5 | $0.00006 | $0.00097 |
Grade A, and why
work-order-preparation 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 — 109 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Work Order Preparation
Use this skill when the technician wants to prepare for a work order — checking that all required parts are available before heading to the job site.
When to Use
- "What do I need for WO-007?"
- "Check parts for WO-003"
- "Am I ready for my next job?"
- "Prepare for WO-010"
- "Are the parts available for WO-007?"
Tools Used by This Skill
This skill uses two capabilities from the Foundry Toolbox:
| Capability | Prefixed tool name |
|---|---|
| Get the work order | work_orders___get_work_order_work_orders__work_order_id__get |
| Check stock for the parts list | inventory___check_stock_batch |
Step 0: Discover tools (REQUIRED before first call this turn)
If either tool isn't already visible in your tool list, run one combined tool_search with limit: 10:
tool_search({"query": "work order parts stock inventory", "limit": 10})
Never run two separate searches — one combined query with limit: 10 returns all needed tools, and they stay callable for the rest of the turn.
Step-by-Step Instructions
Step 1: Fetch the Work Order
Call work_orders___get_work_order_work_orders__work_order_id__get via call_tool with {"work_order_id": "WO-XXX"}.
Extract the parts_needed list — each entry has a part_id and quantity.
If the work order has no parts_needed, skip to Step 3 and note that no parts
are listed for this WO.
Step 2: Check Stock for All Parts
Call inventory___check_stock_batch via call_tool with {"part_ids": [<all part_ids>]} in a single call.
This returns stock status for every part at once — do NOT call check_stock individually.
Compare the required quantity against the available stock for each part.
Classify each part:
- ✅ Ready — stock ≥ required quantity
- ⚠️ Partial — some stock available but less than required
- ❌ Unavailable — out of stock
Step 3: Present the Preparation Checklist
CRITICAL: You MUST use this exact structure with headers and a table. Never output a plain paragraph. This is a multi-source response that combines work order data and inventory data — use visual separators between sections.
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 · 109 lines · 57 tokens per session scan A dbc78385a355
work-order-preparation 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 57 tokens to every session and 974 once invoked, about $0.0003 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.