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/upstream-syncnpx skills add microsoft/intelligent-terminal --skill upstream-syncgit clone --depth 1 https://github.com/microsoft/intelligent-terminalWhat 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.00139 | $0.02969 |
| Opus 5 | $0.00069 | $0.01484 |
| Sonnet 5 | $0.00028 | $0.00594 |
| Haiku 4.5 | $0.00014 | $0.00297 |
Grade A, and why
upstream-sync 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 3d 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 — 164 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Upstream Sync (microsoft/terminal → intelligent-terminal)
Cherry-pick commit-by-commit from https://github.com/microsoft/terminal
into this fork, preserving per-commit attribution, auto-skipping picks
that cancel each other out, and stopping cleanly the moment a
human-judgment conflict appears.
You — the agent reading this file — are the orchestrator. Each step
in the run is a single atomic call into one of the scripts/*.ps1 files.
There is intentionally no PowerShell driver, because every interesting
decision (build-fix vs. open stuck issue, retry vs. bail, finalize vs.
dry-run) wants LLM judgment the operator can audit in your transcript.
When to Use This Skill
- User asks to "sync upstream", "pull from microsoft/terminal", "catch up to upstream", or "run upstream sync".
- A scheduler invokes the agent on a weekly/daily cadence.
- The previous run left an
upstream-sync-stucklabeled issue open and the human has finished resolving the conflict — close the issue (that IS the lock-clear signal) and re-run.
When NOT to Use This Skill
- User wants a one-shot rebase of a single feature branch onto upstream — that's a normal
git rebase, not this skill. - An
upstream-sync-stucklabeled issue is open onmicrosoft/intelligent-terminal— do not re-run; resolve the conflict on the stuck branch first, then close the issue.
Prerequisites
git2.38+ (forcherry-pick --keep-redundant-commits),ghCLI authenticated againstmicrosoft/intelligent-terminal(needs push toupstream-sync/*topic branches + issue/label create), PowerShell 7+ (pwsh) on PATH.originMUST point atmicrosoft/intelligent-terminal. All scripts push tooriginand pass-R microsoft/intelligent-terminalexplicitly. Verify withgit remote -vbefore running.- Full git history on
origin/main(no shallow clone). Watermark discovery walks up to 5000 commits scanning forcherry picked from commit <sha>trailers. In CI, useactions/checkout@v4withfetch-depth: 0. - Windows build host with Visual Studio 2022, Windows SDK,
vswhere, andtools\razzle.cmd/bz. Build is a hard gate before finalize. - No
state.jsonto bootstrap. Watermark = newest(cherry picked from commit <sha>)trailer onorigin/main. If the fork has never usedcherry-pick -x, run the one-time First-time sync.
What ships with it
8 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.
- references/03-conflict-triage.md 7.7 KB
- references/03-known-conflicts.md 2.0 KB
- references/follow-up-pr.md 6.5 KB
- references/recovery-procedures.md 2.9 KB
- references/run-a-sync.md 15 KB
- scripts/02-compute-pending.ps1 8.7 KB runs code
- scripts/03-cherry-pick-one.ps1 12 KB runs code
- scripts/04-try-build.ps1 7.7 KB runs code
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.
- 3d ago First seen · 164 lines · 139 tokens per session scan A a17151f49602
upstream-sync is a skill published in the GitHub repository microsoft/intelligent-terminal (1,908 stars, last pushed yesterday), licensed MIT. It adds 139 tokens to every session and 2,969 once invoked, about $0.0007 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/.
coddy_slash_demo
Examples-only slash skill (Coddy skillsfixture).
a2ui-renderer
Render A2UI (Agent-to-UI declarative surfaces) in CopilotKit v2. Enable the runtime via CopilotRuntime({ a2ui: {...} }), then enable the provider via . Auto-activates via /info — do NOT manually pass renderActivityMessages. createA2UIMessageRenderer ships from @copilotkit/react-core/v2; low-level primitives…
copilotkit-develop
Use when building AI-powered features with CopilotKit v2 -- adding chat interfaces, registering frontend tools, sharing application context with agents, handling agent interrupts, and working with the CopilotKit runtime.
copilotkit-upgrade
Use when migrating a CopilotKit v1 application to v2 -- updating package imports, replacing deprecated hooks and components, switching from GraphQL runtime to AG-UI protocol runtime, and resolving breaking API changes.