Intelligent Terminal is an experimental fork of Windows Terminal that adds native support for AI agents through the Agent Client Protocol. It is for Windows users who want to manage compatible agent command-line tools alongside terminal tabs, profiles, themes, shells, and keyboard shortcuts, and the catalogue entries provide instructions, skills, hooks, and a plugin for working with it.
Borrowing it
Nothing to install: this file belongs to microsoft/intelligent-terminal. 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/intelligent-terminal/main/.github/instructions/rust-wta.instructions.mdgit clone --depth 1 https://github.com/microsoft/intelligent-terminalWrote 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/instructions/microsoft/intelligent-terminal/rust-wta)<a href="https://agentmods.dev/instructions/microsoft/intelligent-terminal/rust-wta"><img src="https://agentmods.dev/badge/instructions/microsoft/intelligent-terminal/rust-wta/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/instructions/microsoft/intelligent-terminal/rust-wta"><img src="https://agentmods.dev/badge/instructions/microsoft/intelligent-terminal/rust-wta.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.00450 | $0.00450 |
| Opus 5.5 | $0.00180 | $0.00180 |
| Sonnet 5.5 | $0.00090 | $0.00090 |
| Haiku 4.5 | $0.00045 | $0.00045 |
Grade A, and why
intelligent-terminal rust-wta.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 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.
What it actually says
WTA Rust conventions
These rules complement rust.instructions.md. Architecture, build commands,
and product behavior are defined in AGENTS.md and tools/wta/AGENTS.md.
Toolchain and dependencies
- Keep the CI
ms-prod-1.93pin intools/wta/rust-toolchain.tomlunless a toolchain update is the explicit task. Repo-root local commands use the installed active toolchain, so do not rely on language or library features newer than Rust 1.93. - New dependencies must build with the repo's static-CRT Windows MSVC configuration.
- Use the explicit Windows target from the repo-level build instructions; do not mix host-target and explicit-target outputs.
- When the shipped dependency graph changes, run
build/scripts/Generate-WtaThirdPartyNotices.ps1with PowerShell 7 and commit bothtools/wta/cgmanifest.jsonand/NOTICE.md.
Runtime behavior
- Resolve state through
runtime_paths::intelligent_terminal_root()and logs throughlogging::log_dir(). Never construct LocalAppData/package paths by hand. - Use structured
tracingtargets and fields. Never log secrets, provider credentials, or session MCP bearer capabilities. - Initialize logging once before substantive startup work and call
logging::shutdown_flush()before everystd::process::exit. - Localize user-facing strings through
t!(...); followrust-localization.instructions.mdfor locale-file changes. - Preserve tab, window, helper, and ACP session identity across asynchronous routing. Do not replace typed identities with loosely related strings.
Testing
- Cover reducers and routing decisions with deterministic unit tests.
- Use mock ACP and render harnesses for protocol/UI behavior instead of timing sleeps or live services.
- Run the explicit-target WTA test command from the repo-level
AGENTS.mdbefore committing or pushing behavior 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.
- 1mo ago First seen · 46 lines · 450 tokens per session scan A 1e9535e9b0e1
intelligent-terminal rust-wta.instructions.md is an instructions file published in the GitHub repository microsoft/intelligent-terminal (2,074 stars, last pushed today), licensed MIT. It adds 450 tokens to every session, about $0.0018 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.
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).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
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 copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.