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/hooks.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/hooks)<a href="https://agentmods.dev/instructions/microsoft/intelligent-terminal/hooks"><img src="https://agentmods.dev/badge/instructions/microsoft/intelligent-terminal/hooks/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/hooks"><img src="https://agentmods.dev/badge/instructions/microsoft/intelligent-terminal/hooks.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.05380 | $0.05380 |
| Opus 5.5 | $0.02152 | $0.02152 |
| Sonnet 5.5 | $0.01076 | $0.01076 |
| Haiku 4.5 | $0.00538 | $0.00538 |
Grade D, and why
intelligent-terminal hooks.instructions.md scanned grade D with 2 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
- Settings in `~/.claude/settings.json` and `.claude/settings.json` Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
if printf '%s' "$command" | grep -qE 'rm -rf /|git reset --hard|git clean -fd|git push.*--force'; then How it starts
The opening of the file, as written. The whole thing — 598 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Hook Authoring Guidelines
Hooks are small, deterministic commands or scripts that run at specific lifecycle events. An awesome hook does one clear job, runs quickly, and makes its side effects explicit.
Folder Structure
A GitHub Copilot hook lives in .github/hooks/ inside your repository:
.github/
└── hooks/
├── block-dangerous-commands.json ← hook config (which event, which script, options)
└── scripts/
├── block-dangerous-commands.sh ← Bash implementation
└── block-dangerous-commands.ps1 ← PowerShell implementation (optional if Bash-only)
You can have multiple .json files — each one registers hooks for one or more events. The host loads all of them.
The Config File
Each .json file maps events to an array of hook entries.
- Command hooks (
type: "command"): run a local script. The host passes event JSON on stdin, your script responds through exit code and stdout.
Config example
{
"version": 1,
"hooks": {
"preToolUse": [
{
"matcher": "bash",
"type": "command",
"bash": "./.github/hooks/scripts/block-dangerous-commands.sh",
"powershell": "./.github/hooks/scripts/block-dangerous-commands.ps1",
"cwd": ".",
"timeoutSec": 5,
"env": {
"BLOCK_MODE": "deny"
}
}
]
}
}
Config fields
| Field | Required | What it does |
|---|---|---|
type |
yes | "command" for scripts |
matcher |
no | Host-level filter — hook only fires when the tool name matches this value (e.g. "bash", "powershell", "edit", "create"). Locally verified working in Copilot CLI v1.0.36; not yet used in repo hook samples. |
bash |
one or both | Command line invoked on Unix / Bash-capable hosts |
powershell |
one or both | Command line invoked on Windows / PowerShell-capable hosts |
cwd |
no | Working directory, relative to repo root |
timeoutSec |
no | Max seconds before the host kills the process (default 30) |
env |
no | Extra process environment variables passed to the script |
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 · 598 lines · 5,380 tokens per session scan D d01563985d7a
intelligent-terminal hooks.instructions.md is an instructions file published in the GitHub repository microsoft/intelligent-terminal (2,074 stars, last pushed today), licensed MIT. It adds 5,380 tokens to every session, about $0.0215 per session on Opus 5.5. A static security scan graded it D with 2 findings (reads agent configuration directories, recursive force delete). 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.