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/lyhcode/agent-skills/iterm2-profilesnpx skills add lyhcode/agent-skills --skill iterm2-profilesgit 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-profiles)<a href="https://agentmods.dev/skills/lyhcode/agent-skills/iterm2-profiles"><img src="https://agentmods.dev/badge/skills/lyhcode/agent-skills/iterm2-profiles.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.00091 | $0.01474 |
| Opus 5 | $0.00046 | $0.00737 |
| Sonnet 5 | $0.00018 | $0.00295 |
| Haiku 4.5 | $0.00009 | $0.00147 |
Grade A, and why
iterm2-profiles 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 — 142 lines — stays where its author put it; the contents beside it link to each section on GitHub.
iTerm2 Profile Management & Visual Customization
Help the user create, manage, and customize iTerm2 profiles — including colors, fonts, key mappings, automatic profile switching, and status bar configuration.
User's Environment
- iTerm2 3.6.8 on macOS, using zsh
- Preferences stored at:
defaults read com.googlecode.iterm2 - Dynamic Profiles directory:
~/Library/Application Support/iTerm2/DynamicProfiles/
Core Concepts
Dynamic Profiles
Dynamic Profiles are the preferred way to manage iTerm2 profiles programmatically. They are JSON (or plist) files placed in ~/Library/Application Support/iTerm2/DynamicProfiles/. iTerm2 watches this directory and reloads automatically on changes.
Each file contains a Profiles array:
{
"Profiles": [
{
"Name": "My Profile",
"Guid": "unique-uuid-here",
"Dynamic Profile Parent Name": "Default",
"Background Color": {
"Red Component": 0.1,
"Green Component": 0.1,
"Blue Component": 0.15,
"Alpha Component": 1,
"Color Space": "sRGB"
},
"Normal Font": "MesloLGS-NF-Regular 15"
}
]
}
Key rules:
- Every profile needs a unique
Guid(useuuidgento generate) Nameis the display name in iTerm2's profile list- Use
Dynamic Profile Parent Nameto inherit from another profile — only override what you want to change - Colors use the
{"Red Component": float, "Green Component": float, "Blue Component": float, "Alpha Component": float, "Color Space": "sRGB"}format, with values from 0.0 to 1.0
Color Scheme Structure
iTerm2 uses 22 named colors in a profile:
| Key | Purpose |
|---|---|
Foreground Color |
Default text |
Background Color |
Terminal background |
Bold Color |
Bold text |
Cursor Color |
Cursor fill |
Cursor Text Color |
Text under cursor |
Cursor Guide Color |
Horizontal line at cursor (set alpha ~0.25) |
Selection Color |
Selection background |
Selected Text Color |
Selected text |
Badge Color |
Badge overlay text |
Link Color |
Clickable links |
Ansi 0 Color – Ansi 15 Color |
The 16 ANSI colors (0-7 normal, 8-15 bright) |
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.
- 3d ago First seen · 142 lines · 91 tokens per session scan A 18908794ad57
iterm2-profiles is a skill published in the GitHub repository lyhcode/agent-skills (2 stars, last pushed 4mo ago), licensed MIT. It adds 91 tokens to every session and 1,474 once invoked, about $0.0005 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…