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.
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 skills/microsoft/intelligent-terminal/pr-integration-testnpx skills add microsoft/intelligent-terminal --skill pr-integration-testgit 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/skills/microsoft/intelligent-terminal/pr-integration-test)<a href="https://agentmods.dev/skills/microsoft/intelligent-terminal/pr-integration-test"><img src="https://agentmods.dev/badge/skills/microsoft/intelligent-terminal/pr-integration-test.svg" alt="Measured on agentmods" 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 | $0.00066 | $0.00874 |
| Opus 5 | $0.00033 | $0.00437 |
| Sonnet 5 | $0.00013 | $0.00175 |
| Haiku 4.5 | $0.00007 | $0.00087 |
Grade A, and why
pr-integration-test 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 5d 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 — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PR Integration Test
Turn a target PR into durable, behavior-focused integration coverage that proves the fixed path, protects existing behavior, and updates the generated release checklist.
When to Use This Skill
- Convert an open or merged PR into cross-component regression coverage.
- Extend
doc/release-check-list.mdand make report scripts check the new rows. - Audit whether a PR's existing tests cover the user-visible behavior rather than only its implementation details.
Prerequisites
- Read
test/e2e/README.mdand reuse the ItE2E framework instead of creating a parallel harness. - Run
pwsh -File test/e2e/bootstrap.ps1 -Checkbefore live E2E validation.
Workflow
Follow workflow.md. Track the phases with a TODO list.
analyze PR -> reconstruct behavior -> audit coverage -> design matrix -> write ItE2E -> wire checklist -> validate -> deliver
Test Design Standard
For every proposed case, record:
| Field | Required answer |
|---|---|
| Contract | What user-visible behavior must remain true? |
| Trigger | What exact action or input exercises it? |
| Boundary | Which real component handoff does this test add beyond unit tests? |
| Oracle | What deterministic observable proves success or suppression? |
| Negative control | What similar input must not trigger the behavior? |
| Existing protection | Which existing tests protect old behavior and must still run? |
| Checklist title | Which exact bold release-checklist title contains the Pester test name? |
Oracle Priority
Prefer the earliest deterministic product-owned signal:
- Protocol/event stream
- Persisted or queryable application state
- Structured diagnostic log
- Rendered terminal or UI state
- LLM-generated text
Use model output only when it is the behavior under test; never use it to prove routing, triggers, suppression, or idempotency.
Release Checklist Contract
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 5d ago First seen · 98 lines · 66 tokens per session scan A 6dbc334e47a8
pr-integration-test is a skill published in the GitHub repository microsoft/intelligent-terminal (1,908 stars, last pushed 2d ago), licensed MIT. It adds 66 tokens to every session and 874 once invoked, about $0.0003 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 skills, from other repositories
configure-coddy
Change Coddy's own configuration when the user asks for it: edit settings, providers, models, logging, permissions, or find, install, update, and remove MCP servers and skills. Stages UCI-style commands and commits only after the user confirms saving. Load when the user explicitly asks to change a Coddy setting, or…
generate-rules
Scan the codebase and generate or refresh focused project rules under .coddy/rules/.
archestra-dev-testing
Use when deciding whether a change needs a test and at which level — unit, backend route-level integration, MSW-backed frontend integration, or e2e — or when reviewing tests for the "fluff test" anti-pattern. Start here before archestra-dev-backend-tests or archestra-dev-e2e.
archestra-dev-e2e
Use when writing, debugging, or running Archestra Playwright e2e tests, API/UI fixtures, WireMock-backed tests, local/CI e2e setup, or test selectors.
coddy_slash_demo
Examples-only slash skill (Coddy skillsfixture).
smoke-test
End-to-end smoke test skill for DeerFlow. Guides through: 1) Pulling latest code, 2) Docker OR Local installation and deployment (user preference, default to Local if Docker network issues), 3) Service availability verification, 4) Health check, 5) Final test report. Use when the user says "run smoke test", "smoke…