Microsoft 365 Agents SDK is a software toolkit for building AI agents that can communicate through channels such as Microsoft 365 Copilot, Teams, web apps, and custom applications. Developers use it to add state, storage, event handling, and channel-specific behavior while choosing their own AI services and models. The catalogue entries are skills and plugins for working with this SDK.
Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/microsoft/Agentsnpx agentmods add skills/microsoft/agents/agents-sdk-typescript-debuggingWrote 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/agents/agents-sdk-typescript-debugging)<a href="https://agentmods.dev/skills/microsoft/agents/agents-sdk-typescript-debugging"><img src="https://agentmods.dev/badge/skills/microsoft/agents/agents-sdk-typescript-debugging/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/agents/agents-sdk-typescript-debugging"><img src="https://agentmods.dev/badge/skills/microsoft/agents/agents-sdk-typescript-debugging.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 6 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Privilege Escalation · line 7 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
- high Privilege Escalation · line 155 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
- medium Rogue Agent · line 22 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
- medium Data Exfiltration · line 132 Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
- medium Data Exfiltration · line 207 Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
- medium Data Exfiltration · line 212 Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
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.00125 | $0.02397 |
| Opus 5.5 | $0.00050 | $0.00959 |
| Sonnet 5.5 | $0.00025 | $0.00479 |
| Haiku 4.5 | $0.00013 | $0.00240 |
Grade A, and why
agents-sdk-typescript-debugging scanned grade A with 1 finding 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 1mo 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -s -o /dev/null -w "%{http_code}" \ How it starts
The opening of the file, as written. The whole thing — 286 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Debugging Agents Built with Microsoft Agents SDK
Overview
Most agent failures fall into one of three categories: the code doesn't build or start, the configuration is wrong, or the agent isn't reachable. Work through this checklist in order — each step confirms a prerequisite for the next.
Checklist
You MUST create a task for each of these items and complete them in order:
- Make sure the code builds successfully.
- Make sure the application starts and runs without crashing.
- Make sure the application opens a port and listens for incoming requests.
- Validate the
.envconfiguration. - Validate the bot's credentials against Azure AD.
- Use the Agents Playground to test the agent end-to-end locally.
1. Build the code
npm run build
Expected: exits with code 0, no errors. Fix any TypeScript or import errors before continuing.
2. Start the application
Run with debug logging enabled to get detailed output from the SDK internals:
DEBUG=agents:* npm start
Or for anonymous local dev:
DEBUG=agents:* node ./dist/index.js
The DEBUG=agents:* flag enables verbose logging across all SDK namespaces. Scope down to reduce noise:
DEBUG=agents:* npm start # everything
DEBUG=agents:authorization:* npm start # all auth (most useful starting point)
DEBUG=agents:msal npm start # token acquisition only
Auth & connections
| Namespace | What it logs |
|---|---|
agents:authorization:connections |
Auth connections loaded at startup (clientId, tenantId, authType); which connection is selected per request |
agents:authorization:manager |
Auth handlers configured at startup (type, scopes); which handler is invoked per request |
agents:authorization:azurebot |
Azure Bot sign-in flow detail (token exchange, magic code, SSO) |
agents:authorization:agentic |
Agentic auth flow detail (token acquisition, OBO) |
agents:authorization |
High-level authorization middleware decisions |
agents:msal |
MSAL token acquisition (token requests, cache hits, OBO) |
agents:jwt-middleware |
Incoming JWT validation |
agents:authConfiguration |
Auth configuration loading |
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.
- 1mo ago First seen · 286 lines · 125 tokens per session scan A 78e1a1bef43e
agents-sdk-typescript-debugging is a skill published in the GitHub repository microsoft/Agents (1,086 stars, last pushed today), licensed MIT. It adds 125 tokens to every session and 2,397 once invoked, about $0.0005 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
azure-identity-ts
Authenticate to Azure services using Azure Identity library for JavaScript (@azure/identity). Use when configuring authentication with DefaultAzureCredential, managed identity, service principals, or interactive browser login.
typescript-development
You MUST activate this skill when working on TypeScript or JavaScript projects.
static-code-analysis-typescript
Creates, reviews, and modernizes static code analysis setups for Node.js and TypeScript repositories, covering ESLint flat config, typescript-eslint, tsconfig, Prettier, import sorting, Husky, lint-staged, package.json quality scripts, and CI quality gates. Use when setting up or auditing linting, formatting…
aidd-error-causes
Use the error-causes library for structured error handling in JavaScript/TypeScript. Use when throwing errors, catching errors, defining error types, or implementing error routing.
error-handling
Apply error handling and recovery patterns in JavaScript/TypeScript or Node.js. Use when implementing error handling, retry logic, or when the user mentions domain errors, error recovery, error escalation.
fp-ts-errors
Handle errors as values using fp-ts Either and TaskEither for cleaner, more predictable TypeScript code. Use when implementing error handling patterns with fp-ts.