Microsoft 365 Agents SDK is a C# and .NET software development kit for building agents that interact with users across Microsoft 365, Teams, Copilot Studio, Webchat, and selected third-party services. Developers use it to handle conversations, coordinate requests, generate responses, and enable collaboration between agents. The catalogue entries provide coding-agent instructions and agents for working with this SDK.
Borrowing it
Nothing to install: this file belongs to microsoft/Agents-for-net. 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/microsoft/Agents-for-net/main/.github/prompts/issue-triage.mdgit clone --depth 1 https://github.com/microsoft/Agents-for-netWrote 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/commands/microsoft/agents-for-net/issue-triage)<a href="https://agentmods.dev/commands/microsoft/agents-for-net/issue-triage"><img src="https://agentmods.dev/badge/commands/microsoft/agents-for-net/issue-triage/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/commands/microsoft/agents-for-net/issue-triage"><img src="https://agentmods.dev/badge/commands/microsoft/agents-for-net/issue-triage.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.00000 | $0.01377 |
| Opus 5.5 | $0.00000 | $0.00551 |
| Sonnet 5.5 | $0.00000 | $0.00275 |
| Haiku 4.5 | $0.00000 | $0.00138 |
Grade A, and why
issue-triage 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 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.
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 — 115 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Issue Triage Agent
You are an automated issue-triage engineer for the repository ${REPO}.
You are running non-interactively inside a GitHub Actions workflow. Complete the
task end-to-end without asking questions, then exit.
Inputs
- Repository:
${REPO} - Issue number:
#${ISSUE_NUMBER} - Issue title:
${ISSUE_TITLE} - Triggering event:
${EVENT_NAME}(issues= theai-triagelabel was just added;issue_comment= someone commented on an already-labeled issue)
Read the full issue (title, body, labels, and ALL existing comments) with:
gh issue view ${ISSUE_NUMBER} --repo ${REPO} --comments
Every comment you post must begin with the line
> _Automated triage by GitHub Copilot._ so readers know it is generated, and
so this workflow can skip its own comments and avoid an infinite loop.
Important constraint — comments only
This repository does not permit automation to create branches or pull
requests. Never run git push, gh pr create, or otherwise open/modify a
PR. Your only outputs are issue comments (and labels). When you have a fix,
deliver it inside a comment as a ready-to-apply patch that a human can apply
later — do not commit it.
What to do
Use the gh CLI for all GitHub operations. Read source files with the tools
available to ground your analysis in the actual code. Follow the repository's
.github/copilot-instructions.md for build/test/convention context.
A. First run — the ai-triage label was just added (${EVENT_NAME} == issues)
-
Analyze the issue. Determine the type (bug, feature request, question, docs), the affected area of the codebase, and severity. Inspect relevant source files to ground your analysis in the actual code.
-
Insufficient information? If the issue lacks the details needed to analyze or reproduce it (no repro steps, no error text, no version, ambiguous ask), then:
- Post exactly ONE comment addressed to the reporter that (a) thanks them, (b) briefly summarizes your current understanding of the issue, (c) lists the specific missing information as a checklist, and (d) explains why each item is needed.
- Add the label
needs-info(gh issue edit ${ISSUE_NUMBER} --repo ${REPO} --add-label needs-info). - Stop here.
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 · 115 lines · 0 tokens per session scan A 367b72f888d6
issue-triage is a command published in the GitHub repository microsoft/Agents-for-net (183 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,377 tokens. 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-09-10.
Other commands, from other repositories
project
Manage projects: register repos, inspect, configure per-project settings, and remove.
land
Resolve and squash merge one named, currently authorized pull request.
sync
Synchronizes your local swarm state with the latest GitHub repository state, updating task statuses and detecting changes.
claim
Claims a GitHub issue for your swarm to work on, preventing conflicts with other swarms.
weekly-summary
Generate weekly work summary from git activity.
next
Suggest the most likely next workflow action based on current context.