agentmods.dev

instrument-observability

instrument-observability is a skill for Claude Code from microsoft/agent365-skills. It costs 210 tokens per session (18,634 once invoked), scanned A, original, MIT.

A workflow that adds Microsoft Agent 365 observability to existing .NET, Node.js, and Python agents. Observability means recording traces and context so an agent's work can be monitored and diagnosed.

In plain words
What is it for?
Use it to install the required packages, connect tracing and context propagation, add instrumentation scopes, configure telemetry, and prepare an agent for Microsoft monitoring.
Why use it?
It makes agent activity visible without changing the agent's main logic, helping developers trace messages, model calls, and tool executions.

Skill for Claude Code ✓ vendor

Written for Claude Code: allowed-tools in frontmatter. Also seen: model in frontmatter; names the AskUserQuestion tool; mentions Claude Code.

Runs only inside its plugin — its command needs a path that Claude Code sets for a plugin’s own hooks and for nothing else. Install the plugin, not this.

Part of the agent365 plugin — 8 skills shipped together

not rated 51repo +1 changed 22d ago A scan 210 tokens original MIT

Good fit Use it to install the required packages, connect tracing and context propagation, add instrumentation scopes, configure telemetry, and prepare an agent for Microsoft monitoring.

Compare 6 skills from other repositories ↓
View source ↗ microsoft/agent365-skills
About the project

Microsoft Agent 365 Skills is a collection of coding-agent skills and MCP configuration for building and operating AI Teammates hosted in Microsoft Teams. It supports the Agent 365 lifecycle, including WorkIQ integration, registration, observability, validation, and local testing, for users of Claude Code and GitHub Copilot.

microsoft/agent365-skills · 51 stars · on GitHub

Install

Getting it into your agent

This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.

Claude Code
/plugin marketplace add microsoft/agent365-skills
Claude Code
/plugin install agent365

Made for: Claude Code.

Or install agent365, the plugin that ships this one along with the rest of its 8 skills.

Wrote 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.

agentmods badge for instrument-observability

README.md
[![agentmods](https://agentmods.dev/badge/skills/microsoft/agent365-skills/instrument-observability/github.svg)](https://agentmods.dev/skills/microsoft/agent365-skills/instrument-observability)
Your own site
<a href="https://agentmods.dev/skills/microsoft/agent365-skills/instrument-observability"><img src="https://agentmods.dev/badge/skills/microsoft/agent365-skills/instrument-observability/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.

agentmods 80×15 button for instrument-observability

Your own site · 80×15
<a href="https://agentmods.dev/skills/microsoft/agent365-skills/instrument-observability"><img src="https://agentmods.dev/badge/skills/microsoft/agent365-skills/instrument-observability.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 210 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 18,634 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00210 $0.18634
Opus 5.5 $0.00084 $0.07454
Sonnet 5.5 $0.00042 $0.03727
Haiku 4.5 $0.00021 $0.01863

Measured 22d ago against content hash 584ee5a4a6aa, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

instrument-observability 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 22d 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.

plugins/agent365/skills/instrument-observability/SKILL.md · 980 lines

How it starts

The opening of the file, as written. The whole thing — 980 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Instrument A365 Observability

Trigger phrases — any of these will activate this skill automatically:

  • "instrument observability for this agent"
  • "add a365 observability to this agent"
  • "add observability to this agent"
  • "set up tracing for this agent"
  • "make this agent visible in microsoft defender"
  • "enable agent 365 telemetry"
  • "wire up opentelemetry for this agent"
  • "add observability to this .net agent"
  • "add observability to this node.js agent"
  • "add a365 observability to this python agent"

Overview

This skill instruments Microsoft Agent 365 observability into an existing agent codebase without disrupting the agent's core logic. It:

  1. Detects the agent type (.NET AgentFramework, Node.js, or Python)
  2. Installs the correct A365 observability packages (core + hosting + optional extensions)
  3. Wires observability in the entry point
  4. Adds BaggageBuilder context or BaggageMiddleware to message handlers
  5. Implements the app-only telemetry token resolver (S2S route) with caching
  6. Adds manual instrumentation scopes (InvokeAgentScope, InferenceScope, ExecuteToolScope — required for store publishing)
  7. Updates configuration files with observability settings
  8. Validates the build passes

Store publishing requirement: The Agent 365 store validation requires InvokeAgentScope, InferenceScope, and ExecuteToolScope to be implemented. This skill wires them.

All changes are additive and idempotent — rerunning the skill is safe. The one exception is legacy delegated telemetry wiring, which this skill replaces (see "Migrating delegated telemetry" in Phase 3).

Telemetry is always exported over the S2S route with an app-only token for the exporting agent identity, whatever the authMode. The S2S route rejects delegated (scp) tokens, so OBO / Agentic User tokens are used only for workload calls (MCP / Graph), never for the exporter. Registered blueprint agent instances need no Agent365.Observability.OtelWrite permission or admin consent (subject to service policy), and neither do AI Teammates, which the route authorizes by their Blueprint's registration. Newer a365 setup all versions skip that grant for both; older versions may still grant it, or print an OtelWrite application-role action item for AI Teammates, and completing it is harmless.

Read the full file on GitHub · 980 lines

Files

What ships with it

3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

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.

  1. 22d ago Changed · +4 lines 584ee5a4a6aa
  2. 1mo ago Changed · -28 lines · +36 tokens per session 1799e9c7afd2
  3. 2mo ago First seen · 1,004 lines · 174 tokens per session scan A 41ce1998d2d0

Subscribe to this mod's changes

instrument-observability is a skill published in the GitHub repository microsoft/agent365-skills (51 stars, last pushed 17d ago), licensed MIT. It adds 210 tokens to every session and 18,634 once invoked, about $0.0008 per session on Opus 5.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.

Analytics and metricsBuilding agents
Related

instrument-observability compared with skills from other repositories

instrument-observability next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
instrument-observabilitymicrosoft/agent365-skillsSkill5117d agoMITA210Claude Code
imagegenopenai/codexSkill134ktodayApache-2.0A113Codex
local-ai-agentsmicrosoft/ai-agents-for-beginnersSkill79kyesterdayMITA200Claude Code, Codex
playwright-climicrosoft/playwrightSkill100kyesterdayApache-2.0A19Claude Code
browser-automationopenclaw/openclawSkill394ktodayMITA36Claude Code
systematic-debuggingobra/superpowersSkill314k4d agoMITA21Claude Code
next-cache-components-adoptionvercel/next.jsSkill143kyesterdayMITA95Claude Code