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/intercom/claude-plugin-external/install-clinpx skills add intercom/claude-plugin-external --skill install-cligit clone --depth 1 https://github.com/intercom/claude-plugin-externalWhat 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.00077 | $0.01708 |
| Opus 5 | $0.00039 | $0.00854 |
| Sonnet 5 | $0.00015 | $0.00342 |
| Haiku 4.5 | $0.00008 | $0.00171 |
Grade B, and why
install-cli scanned grade B 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 2d 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
Do **not** suggest `sudo npm install -g` — installing global packages as root is a known footgun and will cause permissions issues on later updates. How it starts
The opening of the file, as written. The whole thing — 194 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Install Intercom CLI
Install the @intercom/cli package globally and authenticate it against the user's workspace. The CLI complements this plugin: the plugin is for in-conversation MCP usage, while the CLI is for shell access, scripting, and workspace provisioning.
Prerequisites
Before installing, verify the user has:
- Node.js >= 20.6.0 — Run
node --versionto check. If missing or older, direct them to install via nodejs.org or their version manager (nvm, fnm, volta). - npm — Comes bundled with Node.
If node --version returns < 20.6.0, stop and ask the user to upgrade before proceeding. The CLI will not run on older versions.
Step 1: Install Globally
npm install -g @intercom/cli
Verify the install:
intercom --version
If the user gets a permission error (EACCES) on macOS or Linux, they likely have a system Node install. Recommend either:
- Switching to a user-managed Node via nvm/fnm/volta (preferred), or
- Configuring an npm prefix under their home directory.
Do not suggest sudo npm install -g — installing global packages as root is a known footgun and will cause permissions issues on later updates.
Step 2: Authenticate
There are two paths. Ask the user which applies.
Path A: Existing Workspace (most common)
The user has an Intercom workspace and needs to connect the CLI to it.
- Direct them to the Developer Hub.
- Click New app (or select an existing app).
- Under Authentication, copy the Access Token.
- Authenticate one of two ways:
Option 1 — Persistent (recommended for interactive use):
intercom auth login --token "<paste-token-here>"
This stores the token in the OS keyring (Keychain on macOS, Secret Service on Linux, Credential Manager on Windows) so future commands don't need the env var.
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.
- 2d ago First seen · 194 lines · 77 tokens per session scan B a41f8609ea56
install-cli is a skill published in the GitHub repository intercom/claude-plugin-external (2 stars, last pushed 4mo ago), licensed MIT. It adds 77 tokens to every session and 1,708 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it B with 1 finding (asks for root). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…