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/cloudadapter-pipelinegit 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.00412 | $0.00412 |
| Opus 5 | $0.00206 | $0.00206 |
| Sonnet 5 | $0.00082 | $0.00082 |
| Haiku 4.5 | $0.00041 | $0.00041 |
Grade A, and why
Agents-for-net cloudadapter-pipeline.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 3d 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.
What it actually says
CloudAdapter Pipeline Context
When working on the request processing pipeline, delivery modes, or response handling, read docs/full-cloudadapter-sequence-diagram.md for the full mermaid sequence diagram.
Key Design Points
- Normal delivery:
HostResponseAsyncreturnsfalse→ response sent viaConnectorClient. HTTP returns 202 immediately (fire-and-forget path). - Stream delivery:
HostResponseAsyncreturnstrue→ response queued intoChannelResponseQueue→ HTTP thread writes SSE events directly toHttpResponse.Body(blocking path). ChannelResponseQueueis a producer/consumer bridge using an unboundedChannel<IActivity>between the background agent thread and the HTTP response thread.- Middleware chain is recursive — each middleware calls
next()to invoke the next in the pipeline.
Related Source Files
| Component | Path |
|---|---|
| CloudAdapter | src/libraries/Hosting/AspNetCore/CloudAdapter.cs |
| ChannelResponseQueue | src/libraries/Hosting/AspNetCore/ChannelResponseQueue.cs |
| ActivityResponseHandler (SSE writer) | src/libraries/Hosting/AspNetCore/ActivityResponseHandler.cs |
| ChannelServiceAdapterBase | src/libraries/Builder/Microsoft.Agents.Builder/ChannelServiceAdapterBase.cs |
| TurnContext | src/libraries/Builder/Microsoft.Agents.Builder/TurnContext.cs |
| MiddlewareSet | src/libraries/Builder/Microsoft.Agents.Builder/MiddlewareSet.cs |
| Sequence Diagram | docs/full-cloudadapter-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.
- 3d ago First seen · 34 lines · 412 tokens per session scan A f0d523360d92
Agents-for-net cloudadapter-pipeline.instructions.md is an instructions file published in the GitHub repository microsoft/Agents-for-net (177 stars, last pushed 5d ago), licensed MIT. It adds 412 tokens to every session, about $0.0021 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
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.