Azure SDK for Rust is a collection of Rust libraries, organized as separate crates, for interacting with Azure services. Rust developers use the crates and examples to build applications that work with Azure. The catalogue entries provide coding-agent skills, instructions, agents, and MCP integrations for working with the SDK.
Borrowing it
Nothing to install: this file belongs to Azure/azure-sdk-for-rust. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Azure/azure-sdk-for-rust/main/.github/skills/update-emitter/SKILL.mdgit clone --depth 1 https://github.com/Azure/azure-sdk-for-rustWrote 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/azure/azure-sdk-for-rust/update-emitter)<a href="https://agentmods.dev/skills/azure/azure-sdk-for-rust/update-emitter"><img src="https://agentmods.dev/badge/skills/azure/azure-sdk-for-rust/update-emitter.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector pass
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.00016 | $0.00350 |
| Opus 5 | $0.00008 | $0.00175 |
| Sonnet 5 | $0.00003 | $0.00070 |
| Haiku 4.5 | $0.00002 | $0.00035 |
Grade A, and why
update-emitter 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 4d 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.
What it actually says
Update the TypeSpec emitter
Run eng/scripts/Update-Emitter.ps1 to update eng/emitter-package.json to the latest @azure-tools/typespec-rust version and regenerate the lock file.
Regenerating clients
After updating the emitter, service crates should be regenerated to pick up the new version.
Use the repository-pinned tsp-client; do not invoke a globally installed binary. From the repository root, install its locked dependencies:
_TspClientDir="$(pwd)/eng/common/tsp-client"
npm ci --prefix "$_TspClientDir"
Run tsp-client with npm exec --prefix "$_TspClientDir" --no -- while the current directory is the client library root. Service owners should regenerate only their own service crates.
To regenerate a single crate:
cd sdk/{service-directory}/{crate-directory}
npm exec --prefix "$_TspClientDir" --no -- tsp-client update
To regenerate all crates under a service directory from the repository root:
find sdk/{service-directory} -name tsp-location.yaml -execdir \
npm exec --prefix "$_TspClientDir" --no -- tsp-client update \;
See eng/common/tsp-client/README.md for prerequisites, additional commands, and package management details.
After regenerating
- Build and test each affected crate to verify correctness.
- Review any changes to public APIs and update each crate's
CHANGELOG.mdaccordingly.
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.
- 4d ago Changed · +14 lines 250c2333fd43
- 8d ago First seen · 29 lines · 16 tokens per session scan A 24407fe2f06b
update-emitter is a skill published in the GitHub repository Azure/azure-sdk-for-rust (884 stars, last pushed yesterday), licensed MIT. It adds 16 tokens to every session and 350 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-08-30.
Other skills, from other repositories
generate-code-cs
Generate the code from typespec for C#. Parameter: C# SDK repository root location .
translate-a-sample
Translate the Azure SDK sample from python to C# and generate markdownn file for the sample. Parameters: C# SDK repository root; python SDK repository root; Package name: one of Azure.AI.Projects, Azure.AI.Projects.Agents or Azure.AI.Extensions.OpenAI; The name of sample file in Python SDK repository.
author-test
Generate a test given sample. Parameters: C# SDK repository root; Package name: one of Azure.AI.Projects, Azure.AI.Projects.Agents or Azure.AI.Extensions.OpenAI; the sample to use as a starting point for the test.
build-sample-matrix
Build the matrix of all the samples throughout different frameworks.
update-changelog
Update the CHANGELOG.md files of C# projects. Parameters: csroot C# SDK repository root.
cu-sdk-sample-run
Run a specific sample for the Azure AI Content Understanding Java SDK. Use when users want to run a particular sample like Sample02AnalyzeUrl or Sample03AnalyzeInvoice.