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 skills/microsoft/sre-agent/managing-sre-agentnpx skills add microsoft/sre-agent --skill managing-sre-agentgit clone --depth 1 https://github.com/microsoft/sre-agentWrote 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/sre-agent/managing-sre-agent)<a href="https://agentmods.dev/skills/microsoft/sre-agent/managing-sre-agent"><img src="https://agentmods.dev/badge/skills/microsoft/sre-agent/managing-sre-agent.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.00045 | $0.00821 |
| Opus 5 | $0.00023 | $0.00411 |
| Sonnet 5 | $0.00009 | $0.00164 |
| Haiku 4.5 | $0.00005 | $0.00082 |
Grade A, and why
managing-sre-agent 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 today.
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 — 75 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SRE Agent Administration
For this demo, core agent configuration is declared in Bicep
(infra/modules/sre-agent.bicep):
- Agent settings — autonomous mode, High access level, Azure Monitor incident binding
- Connectors —
app-insights,log-analytics,azure-monitor(MonitorClient),learn-docs(Microsoft Learn no-auth MCP) - RBAC — system-assigned managed identity granted Reader, Monitoring Reader, Contributor, and AKS RBAC Cluster Admin on the resource group; the runtime user-assigned identity also has subscription-level Reader so the correlation skill can read Alerts Management and Resource Health event feeds
To change these resources, edit the Bicep and run azd provision.
Custom skills and response plans are defined in
sre-config/agent-config.json and sre-config/skills/. They are applied by
scripts/setup-sre-agent.ps1.
Do not design overlapping response plans around an assumed priority or specificity rule. Treat multiple matches as undefined, keep purpose-built filters mutually exclusive where routing matters, and make any fallback both positively scoped and explicitly exclude every known route.
Post-provision configuration
Run:
.\scripts\setup-sre-agent.ps1
The script applies skills and response plans, then verifies their properties. It also uploads knowledge files, syncs agent-global custom instructions, and enables the Microsoft Learn MCP tools.
The script reads every *.md under sre-config/knowledge-base/, substitutes
@@RG@@ -> the actual resource group, computes a SHA256, and uploads only files
whose content has changed since the last run (cache in
sre-config/knowledge-base/.upload-hashes.json). To add new agent knowledge:
- Drop a new
*.mdfile intosre-config/knowledge-base/ - Use
@@RG@@placeholder anywhere you need the resource group name - Re-run
.\scripts\setup-sre-agent.ps1
To remove a knowledge file: delete the local .md, then delete the corresponding
<name>.md from the agent's Builder UI > Knowledge sources view (the
script does not delete remote files that are no longer present locally).
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.
- today Changed · -1 lines b6b34f98568e
- 4d ago First seen · 76 lines · 45 tokens per session scan A 47c2bcf2d2dc
managing-sre-agent is a skill published in the GitHub repository microsoft/sre-agent (151 stars, last pushed yesterday), licensed MIT. It adds 45 tokens to every session and 821 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-30.
Other skills, from other repositories
cloud-sync
Set up or check claude-mem cloud sync with cmem.ai Pro. Use when the user says "set up cloud sync", "sync my memories", "cmem pro", "cloud backup", "sync status", or wants their memory database backed up or synced to their cmem.ai account.
cognee-cli
Use when the user wants to drive cognee from the terminal with cognee-cli — remember/recall/forget/improve memory commands, managing datasets and config, or database migrations.
add-memory-kind
Add a new business memory kind end-to-end. Pick the storage combination (Markdown / SQLite / LanceDB), pick the markdown strategy (daily-log / skill-named / single-file), then wire up the schema(s), repo(s), and writer(s).
memory-search
Query the raw trajectory SQLite database directly when the built-in memory and history tools are insufficient. Use when you need structured analysis across sessions: finding repeated errors, grouping tool calls by pattern, verifying what was actually executed, or locating specific past commands/decisions that text…
agent-squad-typescript
Use when building or modifying a Node.js / TypeScript app that uses the agent-squad npm package — multi-agent orchestration: orchestrator, agents (all built-in types + GroundedAgent), classifier routing (Bedrock / Anthropic / OpenAI), storage (in-memory / DynamoDB / SQL), retrievers (Amazon KB / Dakera), and tools…
build-with-tinybase
Scaffold, extend, and verify reactive local-first JavaScript or TypeScript applications with TinyBase. Use when choosing TinyBase for in-memory tabular or key-value state, generating an app with create-tinybase, adding schemas or UI bindings, configuring browser or database persistence, configuring MergeableStore…