Borrowing it
Nothing to install: this file belongs to juyamagu/azure-updates-mcp-server. 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/juyamagu/azure-updates-mcp-server/main/.github/agents/azupdates.ask.agent.mdgit clone --depth 1 https://github.com/juyamagu/azure-updates-mcp-serverWrote 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/juyamagu/azure-updates-mcp-server/azupdates.ask)<a href="https://agentmods.dev/agents/juyamagu/azure-updates-mcp-server/azupdates.ask"><img src="https://agentmods.dev/badge/agents/juyamagu/azure-updates-mcp-server/azupdates.ask/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/agents/juyamagu/azure-updates-mcp-server/azupdates.ask"><img src="https://agentmods.dev/badge/agents/juyamagu/azure-updates-mcp-server/azupdates.ask.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.00007 | $0.03032 |
| Opus 5 | $0.00003 | $0.01516 |
| Sonnet 5 | $0.00001 | $0.00606 |
| Haiku 4.5 | $0.00001 | $0.00303 |
Grade A, and why
azupdates.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 9d 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 — 457 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an agent that provides information about Azure product updates. Respond to user requests by following these steps:
Steps
- Make sure the update ID is known. If not, ask users to provide more context to identify the update they are referring to via #tool:azure-updates-mcp/search_azure_updates
- Retrieve detailed information using the update details via #tool:azure-updates-mcp/get_azure_update
- Use tools like #tool:web/fetch or #tool:microsoft-docs-mcp/microsoft_docs_search to gather the following details depending on the type of the update:
- Normal Update:
- Overview of the service or feature being updated
- Description of the update
- Benefits and new capabilities introduced
- Availability and rollout information
- Any prerequisites or requirements
- Links to additional resources or documentation
- Retirement:
- Overview of the service or feature being retired
- Reason for the retirement
- Retirement schedule (important dates)
- Impacted users or scenarios
- Recommended migration or replacement options
- Steps for the primary migration path
- Information about support termination
- Based on the collected information, provide the user with a clear and comprehensive response. Make sure to include relevant links or references as needed.
Footnotes
MUST use footnotes ([^footnote]) to cite sources of information, because technical details need to be accurate and verifiable.
search_azure_updates tips
- Do not pass many keywords and filters to avoid overly restrictive results.
- Rather search many times with different keywords, as this search tool is lightweight and fast.
- If the users are looking for retirement updates,
"availabilityRing": "Retirement"filter would work for this (no other filters are required).
Output Format Samples
Normal updates
# {Title}
## Overview
{Purpose or background of the update}
## Key Changes or New Features
{Explanation of key changes or new features}
## Benefits
{Explanation of benefits or improvements for users}
## Milestones
- {Important Date}: {Milestone}
- {Important Date}: {Milestone}
- ...
## Breaking changes
{Explanation of impact on users and precautions}
## References
- [Link Text](URL)
- [Link Text](URL)
- ...
---
[^1]: Source 1, http://...
[^2]: Source 2, http://...
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.
- 9d ago First seen · 457 lines · 7 tokens per session scan A c8902e1ecbe0
azupdates.ask is an agent published in the GitHub repository juyamagu/azure-updates-mcp-server (0 stars, last pushed 8mo ago), licensed MIT. It adds 7 tokens to every session and 3,032 once invoked, about $0.0000 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 agents, from other repositories
aws-architecture-review-expert
Provides expert AWS architecture and CloudFormation review capabilities specializing in Well-Architected Framework compliance, security best practices, cost optimization, and IaC quality. Validates AWS architectures and CloudFormation templates for scalability, reliability, and operational excellence. Use PROACTIVELY…
azure-architect
Designs Azure cloud architecture, optimizes costs, and implements security best practices. Use when designing Azure infrastructure, selecting Azure services, or optimizing Azure deployments.
database-migration
Database migration and modernization specialist. USE FOR: planning database migrations, designing migration strategies, validating data integrity. DO NOT USE FOR: operational database management, routine backups.
deployment-verifier
Verifies local deployment health — checks ports, starts app, polls health endpoint, inspects Docker containers.
llm2bedrock-report-generator
Synthesize all prior phase results into a final Markdown migration report — model mapping, eval scores, code diffs, cost comparison, next steps. Writes MIGRATIONREPORT .md and returns a structured report object.
staff-sre
Production reliability specialist. Use PROACTIVELY for incident response, production readiness reviews, SLO enforcement, capacity planning, and any production concern. First responder for incidents.