intelligent-terminal: Instructions file for GitHub Copilot

.github/instructions/post-merge-cleanup.instructions.md

intelligent-terminal post-merge-cleanup.instructions.md is an instructions file for GitHub Copilot from microsoft/intelligent-terminal. It costs 319 tokens per session, scanned A, original, MIT.

A set of instructions for cleaning up a Git worktree after its pull request has been merged. A worktree is another checkout of the same repository, often used for separate tasks.

In plain words
What is it for?
It is for checking a merged worktree, uninstalling packages tied to it, removing the worktree, and deleting its local branch safely.
Why use it?
It helps remove related installed packages and files without deleting uncommitted work, unrelated packages, or a regular installation by mistake.

Instructions file for GitHub Copilot ✓ vendor

Written for GitHub Copilot: a Copilot instructions file.

This is microsoft/intelligent-terminal's own configuration. It tells GitHub Copilot how to work on intelligent-terminal itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything intelligent-terminal configures →

About the project

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.

microsoft/intelligent-terminal · 2,056 stars · on GitHub · devblogs.microsoft.com

Reuse

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.

Copy the file
curl -O https://raw.githubusercontent.com/microsoft/intelligent-terminal/main/.github/instructions/post-merge-cleanup.instructions.md
Clone the repo
git clone --depth 1 https://github.com/microsoft/intelligent-terminal

Made for: GitHub Copilot.

Wrote 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.

agentmods badge for intelligent-terminal post-merge-cleanup.instructions.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/microsoft/intelligent-terminal/post-merge-cleanup/github.svg)](https://agentmods.dev/instructions/microsoft/intelligent-terminal/post-merge-cleanup)
Your own site
<a href="https://agentmods.dev/instructions/microsoft/intelligent-terminal/post-merge-cleanup"><img src="https://agentmods.dev/badge/instructions/microsoft/intelligent-terminal/post-merge-cleanup/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.

agentmods 80×15 button for intelligent-terminal post-merge-cleanup.instructions.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/microsoft/intelligent-terminal/post-merge-cleanup"><img src="https://agentmods.dev/badge/instructions/microsoft/intelligent-terminal/post-merge-cleanup.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 319 This file is loaded in full into every session.
When invoked 319 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00319 $0.00319
Opus 5.5 $0.00128 $0.00128
Sonnet 5.5 $0.00064 $0.00064
Haiku 4.5 $0.00032 $0.00032

Measured today against content hash a4d7fdd3279d, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

intelligent-terminal post-merge-cleanup.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 today.

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.

.github/instructions/post-merge-cleanup.instructions.md · 31 lines

What it actually says

Post-merge cleanup

Run when asked to clean up a worktree after its PR is merged.

1. Uninstall packages from the worktree

  • Resolve the exact worktree folder and use Get-AppxPackage to find packages whose InstallLocation is that folder or a child directory. Match the full directory boundary, not a partial path or package display name.
  • If the user's regular installation uses this folder, stop and report that dependency instead of uninstalling it or removing its backing worktree.
  • Preserve any needed application data before uninstalling; removal can delete package-private settings and sessions. Leave unrelated packages untouched.
  • Close only the matching apps, uninstall each package by its exact PackageFullName using Remove-AppxPackage, and confirm removal succeeded. If a package cannot be removed, stop before deleting its backing folder.

2. Remove the worktree and local branch

  • Check for uncommitted or untracked work and commits not included in the merged PR. Preserve them rather than discarding them.
  • From another checkout, run git worktree remove <worktree-path>, then delete its local branch with git branch -d <branch>. If Git refuses either operation, report the blocker instead of forcing deletion.
  • Report what was removed and anything left behind.
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.

  1. today First seen · 31 lines · 319 tokens per session scan A a4d7fdd3279d

Subscribe to this mod's changes

intelligent-terminal post-merge-cleanup.instructions.md is an instructions file published in the GitHub repository microsoft/intelligent-terminal (2,056 stars, last pushed today), licensed MIT. It adds 319 tokens to every session, about $0.0013 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-10-16.

Related

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).

microsoft/vscode · 9,649 tokens

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.

vercel/next.js · 7,257 tokens

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).

microsoft/vscode · 5,262 tokens

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.

langchain-ai/langchain · 4,680 tokens

deepseek-harness AGENTS.md

AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.

deepseek-ai/deepseek-harness · 4,159 tokens

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).

microsoft/vscode · 2,731 tokens