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 skills add lyhcode/agent-skills --skill iterm2-shell-setupgit clone --depth 1 https://github.com/lyhcode/agent-skillsWrote 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/lyhcode/agent-skills/iterm2-shell-setup)<a href="https://agentmods.dev/skills/lyhcode/agent-skills/iterm2-shell-setup"><img src="https://agentmods.dev/badge/skills/lyhcode/agent-skills/iterm2-shell-setup/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/lyhcode/agent-skills/iterm2-shell-setup"><img src="https://agentmods.dev/badge/skills/lyhcode/agent-skills/iterm2-shell-setup.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.00109 | $0.01534 |
| Opus 5.5 | $0.00044 | $0.00614 |
| Sonnet 5.5 | $0.00022 | $0.00307 |
| Haiku 4.5 | $0.00011 | $0.00153 |
Grade A, and why
iterm2-shell-setup scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -L https://iterm2.com/shell_integration/zsh -o ~/.iterm2_shell_integration.zsh How it starts
The opening of the file, as written. The whole thing — 161 lines — stays where its author put it; the contents beside it link to each section on GitHub.
iTerm2 Shell Integration & Environment Setup
Help the user install, configure, and troubleshoot iTerm2's shell integration features, plus tmux integration and remote SSH setup.
User's Environment
- iTerm2 3.6.8 on macOS, using zsh
- Shell integration: not currently installed
What Shell Integration Enables
Shell integration is the foundation for many of iTerm2's best features. Without it, these features don't work:
- Command marks — Navigate between prompts with Cmd+Shift+Up/Down
- Command status — Red/blue marks showing success/failure of each command
- Automatic profile switching — Switch profiles based on hostname/user/path
- Recent directories — Frecency-sorted directory list in the toolbelt
- Command history — Searchable history across all sessions
- File download — Right-click to download remote files via SCP
- Long command alerts — Notification when a command finishes after N seconds
- Captured output — Filter and interact with command output
- Auto Composer — Native text editing for command input
Installation
Method 1: Automatic (Recommended)
iTerm2 can load shell integration automatically without modifying shell config files:
Settings > Profiles > General > Command > enable "Load shell integration automatically"
This injects the integration at session start without touching ~/.zshrc.
Method 2: Menu Install
iTerm2 > Install Shell Integration
This downloads the scripts and adds a source line to ~/.zshrc.
Method 3: Manual Install for zsh
Add to ~/.zshrc:
test -e "${HOME}/.iterm2_shell_integration.zsh" && source "${HOME}/.iterm2_shell_integration.zsh"
Then download the script:
curl -L https://iterm2.com/shell_integration/zsh -o ~/.iterm2_shell_integration.zsh
Verification
After installation, check that it's working:
- Open a new iTerm2 tab
- You should see a blue triangle mark at the left of each prompt
- Run
echo $ITERM_SESSION_ID— should output a value - Check:
type iterm2_print_user_varsshould find the function
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.
- 1mo ago First seen · 161 lines · 109 tokens per session scan A d906bf0e5611
iterm2-shell-setup is a skill published in the GitHub repository lyhcode/agent-skills (2 stars, last pushed 6mo ago), licensed MIT. It adds 109 tokens to every session and 1,534 once invoked, about $0.0004 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
component-fixtures
Use when creating or updating component fixtures for screenshot testing or their shared infrastructure, or when designing UI components to be fixture-friendly. Covers fixture file structure, theming, service setup, CSS scoping, async rendering, validation, and common pitfalls.