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 instructions/microsoft/agents-for-net/oauth-flowsgit clone --depth 1 https://github.com/microsoft/Agents-for-netWhat 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.00550 | $0.00550 |
| Opus 5 | $0.00275 | $0.00275 |
| Sonnet 5 | $0.00110 | $0.00110 |
| Haiku 4.5 | $0.00055 | $0.00055 |
Grade A, and why
Agents-for-net oauth-flows.instructions.md 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 2d 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 — 40 lines — stays where its author put it; the contents beside it link to each section on GitHub.
OAuth & User Sign-In Flow Context
When working on OAuth, token exchange, or user sign-in code, reference these sequence diagrams:
docs/teams-sso-sequence-diagram.md— High-level Teams SSO scenarios (SignedIn, No Consent, Consent Required, Exchange Failure)docs/oauth-internal-sequence-diagram.md— Detailed internal flow through UserAuthorization → UserAuthorizationDispatcher → AzureBotUserAuthorization → OAuthFlow → IUserTokenClient
Key Design Points
- Sign-in is a multi-turn operation — flow state is stored between turns and deleted on completion or failure.
- The Token Service Client caches successful tokens from
GetTokenOrSignInResource. - If OBO is configured, OBO is performed on the token returned by Token Service prior to setting the Turn Token.
- A Continuation Activity is stored when sign-in starts and replayed proactively after successful token acquisition.
- ConsentRequired (412) triggers Teams to prompt the user, followed by a
signin/verifyStateinvoke with a magic code. - Non-consent exchange failures return 400 — Teams will NOT retry.
Related Source Files
| Component | Path |
|---|---|
| UserAuthorization (App-level) | src/libraries/Builder/Microsoft.Agents.Builder/App/UserAuth/UserAuthorization.cs |
| UserAuthorizationDispatcher | src/libraries/Builder/Microsoft.Agents.Builder/UserAuth/UserAuthorizationDispatcher.cs |
| AzureBotUserAuthorization | src/libraries/Builder/Microsoft.Agents.Builder/UserAuth/TokenService/AzureBotUserAuthorization.cs |
| OAuthFlow | src/libraries/Builder/Microsoft.Agents.Builder/UserAuth/TokenService/OAuthFlow.cs |
| UserTokenClientWrapper | src/libraries/Builder/Microsoft.Agents.Builder/UserAuth/TokenService/UserTokenClientWrapper.cs |
| IUserTokenClient | src/libraries/Client/Microsoft.Agents.Connector/IUserTokenClient.cs |
| OBOExchange | src/libraries/Builder/Microsoft.Agents.Builder/UserAuth/OBOExchange.cs |
| Authentication.Msal | src/libraries/Authentication/Authentication.Msal/ |
| High-level diagrams | docs/teams-sso-sequence-diagram.md |
| Detailed internal diagrams | docs/oauth-internal-sequence-diagram.md |
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.
- 2d ago First seen · 40 lines · 550 tokens per session scan A d5e1d5493d70
Agents-for-net oauth-flows.instructions.md is an instructions file published in the GitHub repository microsoft/Agents-for-net (177 stars, last pushed 4d ago), licensed MIT. It adds 550 tokens to every session, about $0.0028 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 instructions, from other repositories
spellbook AGENTS.md
Instructions for majiayu000/spellbook, covering spellbook agent contract, routing, scope rules, threads long-run guardrails and validation.
open-supermarkets AGENTS.md
Instructions for abracadabra50/open-supermarkets, covering agent integration guide, supported frameworks, quick integration, 1. add as skill and 2. agent calls commands.
helm copilot-instructions.md
Instructions for PetePeter/helm, covering gamepad-cli-hub — copilot instructions, project purpose, system overview, data flow pipeline and key controls.
flyto-core CLAUDE.md
Instructions for flytohub/flyto-core, covering claude notes, cross-agent handoff and shared code intelligence.
fusion-skills AGENTS.md
AGENTS.md instructions for CrowdStrike/fusion-skills, covering agents.md, what this is, prerequisites, repository structure and skills ecosystem.
aeon CLAUDE.md
Instructions for aeonfun/aeon, covering aeon, how aeon works, strategy, voice and soul file hierarchy (read in this order).