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/skills/release-notes/SKILL.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/skills/microsoft/intelligent-terminal/release-notes)<a href="https://agentmods.dev/skills/microsoft/intelligent-terminal/release-notes"><img src="https://agentmods.dev/badge/skills/microsoft/intelligent-terminal/release-notes/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/skills/microsoft/intelligent-terminal/release-notes"><img src="https://agentmods.dev/badge/skills/microsoft/intelligent-terminal/release-notes.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00073 | $0.01962 |
| Opus 5.5 | $0.00029 | $0.00785 |
| Sonnet 5.5 | $0.00015 | $0.00392 |
| Haiku 4.5 | $0.00007 | $0.00196 |
Grade A, and why
release-notes 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.
How it starts
The opening of the file, as written. The whole thing — 121 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release Notes Generator
Generate polished, user-facing release notes for Intelligent Terminal releases by analyzing git history, PR metadata, and issue links.
When to Use This Skill
- User asks to write release notes or changelog
- User asks "what's new since last release"
- User asks to prepare a release
- User asks to summarize recent commits for end-users
Step-by-Step Workflow
Phase 1: Identify the Commit Range
The base is the latest release tag (the vX.Y.Z sequence, e.g. v0.1.18) and the head is main. The range is everything between them.
- Find the latest release tag — the newest 3-part
vX.Y.Ztag that is merged intomain. The filter is what keeps this reliable: it excludes upstream Windows Terminalv1.xtags (not on this fork's history) and the legacy four-partv0.1.NNNN.0tags (stale, some point at ancient upstream commits). Do not anchor onstable— it is a cherry-picked subset that lags the release tag.git tag --list 'v*' --merged main --sort=-v:refname | grep -E '^v[0-9]+\.[0-9]+\.[0-9]+$' | head -1
(The user may override with a specific base commit/tag; if the plaingit tag --list 'v*' --merged main | Where-Object { $_ -match '^v\d+\.\d+\.\d+$' } | Sort-Object { [version]($_ -replace '^v','') } | Select-Object -Last 1git taglist looks nothing like the above — e.g. onlyv1.xshows up — the--merged mainfilter is being skipped.) - List all commits from the base tag to
main(replace$BASE_TAGwith the tag from step 1):git log --oneline --reverse "$BASE_TAG"..main - Extract PR numbers from commit messages (pattern:
(#NNN)).
The
0.1.xxxx.0build number is injected by CI at release time; the human-facing version is thevX.Y.Ztag sequence.
Phase 2: Enrich with PR Metadata
For each PR number, look up linked issues and author info (replace PR_NUMBER and OWNER/REPO):
gh pr view PR_NUMBER --repo OWNER/REPO --json number,title,body,author,closingIssuesReferences
What ships with it
4 files 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.
- 1mo ago First seen · 121 lines · 73 tokens per session scan A 0720817ff884
release-notes is a skill published in the GitHub repository microsoft/intelligent-terminal (2,074 stars, last pushed today), licensed MIT. It adds 73 tokens to every session and 1,962 once invoked, about $0.0003 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 skills, from other repositories
public-plugin-packaging
Use when packaging an Agentlas agent repo for public GitHub release, Codex plugin submission, Claude adapter distribution, or one-line terminal installation.
release-cut
Cut a new pi-agent-dashboard release: promote ## [Unreleased] in CHANGELOG.md, bump every workspace package.json per SemVer, commit, tag v , and push — triggering the Release workflow that publishes every non-private workspace, builds the Electron artifacts, and creates a GitHub Release. Use on "cut a release"…
release-revoke
Revoke or rollback a pi-agent-dashboard release: delete the GitHub Release, remove the git tag locally and on origin, deprecate the npm version (npm unpublish is blocked after 72h), and optionally revert the release commit. Use when the user says "revoke release", "rollback release", "delete release", "unpublish…
git-workflow
Use when naming or scoping a branch, writing or fixing a commit message, picking the gitmoji for a commit, untangling history (rebase versus merge versus squash), or cutting a versioned release — the portable git-convention layer for any repo. Covers gitmoji + Conventional Commits, SemVer tags, branch hygiene…
kirocrew-prepare-pr
LOAD THIS FOR EVERY KIRO CREW PR you open or update (Kiro Crew repo only; not other repos or CRs). Runs the whole loop — issue + tier, commit, sync, squash, push, drive CI and AI review to green, fix a red main, arm auto-merge and watch it land (24h). 'push my changes' = prepare-only.
pypi-release
This skill should be used when releasing tunacode-cli to PyPI. It keeps the existing local release checks, then hands the actual PyPI upload to a GitHub Actions workflow that uses the repository's PYPIAPITOKEN secret.