Agent skill

Intercom Security Basics

by jeremylongshore in jeremylongshore/tons-of-skills-marketplace

Apply Intercom security best practices for tokens, webhook verification, and scopes.

MITAuto-check: notesBackend & APIs

Install Intercom Security Basics

skills CLI
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill intercom-security-basics -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install jeremylongshore/tons-of-skills-marketplace intercom-security-basics --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/.curated/intercom-security-basics .claude/skills/intercom-security-basics && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
intercom-security-basics
GitHub stars
2.8k
Token cost
~1.7k tokens
SKILL.md length
581 words
Files
3 (incl. references)
Skills in repo
3,342
Repo updated
First seen
Licence
MIT

At a glance

Apply Intercom security best practices for tokens, webhook verification, and scopes.

  • Works in 5 steps: Secure Token Storage → Webhook Signature Verification… → Identity Verification (User Hash) → …
  • Securing access tokens
  • SKILL.md covers Overview, Prerequisites, Instructions and Output, plus 5 more sections
  • Calls git, curl and jq; reaches api.intercom.io; needs INTERCOM_ACCESS_TOKEN and INTERCOM_IDENTITY_SECRET

What it does

Intercom Security Basics is an agent skill from jeremylongshore/tons-of-skills-marketplace. Apply Intercom security best practices for tokens, webhook verification, and scopes. Use when securing access tokens, implementing webhook signature validation, or configuring least-privilege OAuth scopes. Trigger with phrases like "intercom security", "intercom secrets", "secure intercom", "intercom webhook signature", "intercom token rotation".

Its SKILL.md is about 1.7k tokens, which your agent loads only when the skill is triggered. The skill folder holds 3 other files, including reference files (for example `references/examples.md` and `references/implementation.md`). Compatibility notes: Designed for Claude Code

It sits in Backend & APIs, covering Webhooks and OAuth and OpenID Connect. It works with Intercom. The repository describes itself as: Model-agnostic agent-skills platform with a harness-free canonical layer, verified adapters, and the ccpi package manager. Explore at tonsofskills.com. The licence is MIT.

When your agent uses it

  • Securing access tokens
  • Implementing webhook signature validation
  • Configuring least-privilege OAuth scopes
  • With phrases like intercom security

Example prompts

  • “intercom security”
  • “intercom secrets”
  • “secure intercom”
  • “/intercom-security-basics”

Requirements

  • A credential in INTERCOM_ACCESS_TOKEN
  • A credential in INTERCOM_WEBHOOK_SECRET
  • Compatibility (from SKILL.md): Designed for Claude Code
  • Pre-approved tools (allowed-tools): Read, Write, Grep

Workflow steps

5 steps, taken from the step headings in SKILL.md.

  1. Secure Token Storage
  2. Webhook Signature Verification (X-Hub-Signature)
  3. Identity Verification (User Hash)
  4. Least-Privilege OAuth Scopes
  5. Token Rotation Procedure

What it can do on your machine

Read from SKILL.md and the folder at commit 80f86df. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Read
    • Write
    • Grep

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • git
    • curl
    • jq

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Hosts in commands or code, which the agent is likely to contact:

    • api.intercom.io

    Also links to:

    • developers.intercom.com

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names these keys or tokens, usually read from environment variables:

    • INTERCOM_ACCESS_TOKEN
    • INTERCOM_IDENTITY_SECRET
    • INTERCOM_WEBHOOK_SECRET
    • NEW_TOKEN

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

  • Compatibility

    Designed for Claude Code

    From compatibility in the SKILL.md frontmatter.

Context cost

Intercom Security Basics loads about 1.7k tokens when it runs, and up to ~3.5k if it reads all its reference files. Until then it costs about 93 tokens; SKILL.md has 581 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~93
When it runs · the whole SKILL.md, loaded when a task matches
~1.7k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~3.5k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

  • NoteMentions a .env fileSKILL.md:50
    Store every secret in `.env` (or a secret manager) and never commit it.
  • NoteMentions a .env fileSKILL.md:53
    # .env (NEVER commit to git)
  • NoteMentions a .env fileSKILL.md:59
    .env
  • NoteMentions a .env fileSKILL.md:60
    .env.local
  • NoteMentions a .env fileSKILL.md:61
    .env.*.local
  • NoteMentions a .env fileSKILL.md:120
    - A `.env` (or secret-manager entry) holding `INTERCOM_ACCESS_TOKEN`,
  • NoteMentions a .env fileSKILL.md:121
    `, and `INTERCOM_IDENTITY_SECRET`, with `.env` patterns
  • NoteMentions a .env fileSKILL.md:134
    - [ ] `.env` files in `.gitignore`
  • NoteMentions a .env fileSKILL.md:157
    rom zero** — store the three secrets in `.env`

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from jeremylongshore/tons-of-skills-marketplace at commit 80f86df, republished under its MIT licence (© jeremylongshore). 581 words, ~1,693 tokens.

Download SKILL.mdSave it as .claude/skills/intercom-security-basics/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.
name
intercom-security-basics
description
Apply Intercom security best practices for tokens, webhook verification, and scopes. Use when securing access tokens, implementing webhook signature validation, or configuring least-privilege OAuth scopes. Trigger with phrases like "intercom security", "intercom secrets", "secure intercom", "intercom webhook signature", "intercom token rotation".
allowed-tools
Read, Write, Grep
compatibility
Designed for Claude Code
version
1.6.0
license
MIT
author
Jeremy Longshore <jeremy@intentsolutions.io>
tags
saas, support, messaging, intercom

Intercom Security Basics

Overview

Security best practices for Intercom access tokens, webhook signature verification, Identity Verification (HMAC), and least-privilege OAuth scopes.

The full code for each control lives in references/ so this file stays a fast, high-level checklist you can follow end-to-end, then drill into for depth:

Prerequisites

  • Intercom access token or OAuth credentials
  • Understanding of HMAC cryptographic signatures
  • Access to Intercom Developer Hub

Instructions

Step 1: Secure Token Storage

Store every secret in .env (or a secret manager) and never commit it.

bash
# .env (NEVER commit to git)
INTERCOM_ACCESS_TOKEN=dG9rOmFiY2RlZmdoaQ==
INTERCOM_WEBHOOK_SECRET=your-webhook-signing-secret
INTERCOM_IDENTITY_SECRET=your-identity-verification-secret

# .gitignore (mandatory entries)
.env
.env.local
.env.*.local

Then scan history for anything already leaked — use Grep (or the shell) to search committed content for token markers:

bash
git log --all -p | grep -i "INTERCOM_ACCESS_TOKEN\|dG9r" | head -5
# If found: rotate the token immediately, then use git-filter-repo to remove it.
Step 2: Webhook Signature Verification (X-Hub-Signature)

Intercom signs webhook notifications with HMAC-SHA1 using X-Hub-Signature. Verify it on every incoming webhook against the raw request body, using a timing-safe comparison, and reject mismatches with 401:

typescript
const expectedSignature = "sha1=" + crypto
  .createHmac("sha1", secret)
  .update(payload)   // payload = raw Buffer, not parsed JSON
  .digest("hex");
return crypto.timingSafeEqual(Buffer.from(signature), Buffer.from(expectedSignature));

Full Express handler: implementation.md — Webhook Signature Verification.

Step 3: Identity Verification (User Hash)

Identity Verification blocks impersonation by requiring an HMAC-SHA256 of the user's identifier, generated server-side only:

typescript
crypto.createHmac("sha256", process.env.INTERCOM_IDENTITY_SECRET!)
  .update(userId)
  .digest("hex");

Return this user_hash alongside app_id and user_id for Messenger boot. Full code: implementation.md — Identity Verification.

Step 4: Least-Privilege OAuth Scopes

Only request the scopes your app actually uses — excess scopes widen the blast radius of a leaked token. The full use-case → scope mapping is in implementation.md — Least-Privilege OAuth Scopes. For example, a read-only contacts integration needs just Read contacts, not full CRM read/write.

Step 5: Token Rotation Procedure

Rotate by adding the new token to your secret manager and deploying before revoking the old one, so no window exists without a live token. Full procedure (AWS / GCP / Vault examples + verification curl): implementation.md — Token Rotation Procedure.

Output

Applying this skill produces:

  • A .env (or secret-manager entry) holding INTERCOM_ACCESS_TOKEN, INTERCOM_WEBHOOK_SECRET, and INTERCOM_IDENTITY_SECRET, with .env patterns added to .gitignore.
  • A webhook route that returns 200 for valid X-Hub-Signature deliveries and 401 for missing or forged signatures.
  • Server-side user_hash generation wired into the Messenger boot settings.
  • An OAuth app requesting only least-privilege scopes.
  • A documented, tested token-rotation runbook.

The end state is the completed Security Checklist below, every box ticked.

Show full SKILL.md (227 more words)Show less

Security Checklist

  • Access tokens stored in environment variables or secret manager
  • .env files in .gitignore
  • Different tokens for dev/staging/production workspaces
  • Webhook signatures verified on every request (X-Hub-Signature)
  • Identity Verification enabled (user_hash)
  • OAuth scopes are minimal (least privilege)
  • Token rotation procedure documented and tested
  • Git history scanned for leaked credentials
  • HTTPS enforced for all webhook endpoints

Error Handling

Security IssueDetectionMitigation
Leaked token in gitgit log -p | grep dG9rRotate immediately, remove from history
Invalid webhook signature401 from verificationCheck secret matches Developer Hub
Missing Identity VerificationIntercom dashboard warningImplement user_hash on server
Excessive OAuth scopesScope auditRemove unnecessary scopes
Token never rotatedAge trackingSchedule quarterly rotation

Examples

Four end-to-end walkthroughs live in references/examples.md:

  1. Secure a fresh integration from zero — store the three secrets in .env and prove none are staged.
  2. Scan an existing repo for a leaked token — git log --all -p | grep for token markers before shipping.
  3. Add webhook verification to an Express app — reject forged payloads with 401 via X-Hub-Signature.
  4. Turn on Identity Verification for the Messenger — server-side user_hash to stop impersonation.

Quick sanity check that a rotated token is live:

bash
curl -s https://api.intercom.io/me \
  -H "Authorization: Bearer $NEW_TOKEN" | jq '.type'
# Should return "admin"

Resources

Next Steps

For production deployment hardening beyond these basics, see the intercom-prod-checklist skill, which covers rate limiting, error monitoring, and staged rollout for the same integration.

© jeremylongshore, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 2 other files (references) in skills/.curated/intercom-security-basics of jeremylongshore/tons-of-skills-marketplace.

  • SKILL.md
  • references/examples.md
  • references/implementation.md

Open the folder on GitHubat commit 80f86df

Compare with similar skills

Intercom Security Basics next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Intercom Security Basics compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Intercom Security Basics this skilljeremylongshore/tons-of-skills-marketplace2.8k—~1.7kAutomated safety check: NotesMIT
Stripe Best Practiceskanchengw/cnllm1752 repos~925Automated safety check: PassApache-2.0
Discord Php Bot Securitydiscord-php/DiscordPHP1.1k—~1.2kAutomated safety check: NotesMIT
GitHub OAuth Nango IntegrationAgentWorkforce/relay8671 repos~3.4kAutomated safety check: PassApache-2.0
Add OAuth Integrationrome-os/rome737—~3.6kAutomated safety check: PassMIT
Triggers GuideOtoDock/oto-dock190—~3kAutomated safety check: PassCustom licence

Similar skills

  • Stripe Best Practices

    kanchengw/cnllm

    Guides Stripe integration decisions — API selection (Checkout Sessions vs PaymentIntents), Connect platform setup (Accounts v2, controller properties), billing/subscriptions, Treasury financial…

    175 GitHub starsUsed in 2 repos~925 tokens
    Backend & APIsAuto-check passed
  • Discord Php Bot Security

    discord-php/DiscordPHP

    Audit checklist for DiscordPHP bots and API libraries — stop the bot token leaking to third-party APIs or logs, keep secrets out of customids and exception messages, use constant-time comparison and…

    1.1k GitHub stars~1.2k tokensUpdated 3 days ago
    Backend & APIsAuto-check: notes
  • GitHub OAuth Nango Integration

    AgentWorkforce/relay

    A skill your agent uses when implementing GitHub OAuth + GitHub App authentication with Nango - provides two-connection pattern for user login and repo access with webhook handling

    867 GitHub starsUsed in 1 repo~3.4k tokens
    Backend & APIsAuto-check passed
  • Add a new Rome-managed OAuth integration for a third-party service so a user can delegate access by clicking Connect, and Rome can act on the service with the delegated token (the GitHub/Slack model…

    737 GitHub stars~3.6k tokensUpdated today
    Backend & APIsAuto-check passed
  • Triggers Guide

    OtoDock/oto-dock

    Reference for the triggers-mcp tools — the trigger↔task and trigger↔notification patterns with full call shapes, vendor-subscribed (OAuth) triggers and eventfilter rules, payload placeholders…

    190 GitHub stars~3k tokensUpdated yesterday
    Backend & APIsAuto-check passed
  • Validate a Rome-managed OAuth integration end-to-end — prove a user can click Connect and Rome ends up holding a delegated token it can use to call the provider's API.

    737 GitHub stars~2k tokensUpdated today
    Backend & APIsAuto-check: notes

More from jeremylongshore/tons-of-skills-marketplace

All 3,342 skills in this repo
  • Performing Security Code Review

    jeremylongshore/tons-of-skills-marketplace

    Execute this skill enables AI assistant to conduct a security-focused code review using the security-agent plugin.

    2.8k GitHub starsUsed in 2 repos~1.3k tokens
    Auto-check: notes
  • Adapting Transfer Learning Models

    jeremylongshore/tons-of-skills-marketplace

    Build this skill automates the adaptation of pre-trained machine learning models using transfer learning techniques.

    2.8k GitHub stars~1.1k tokensUpdated today
    Auto-check passed
  • Agent Context Loader

    jeremylongshore/tons-of-skills-marketplace

    Execute proactive auto-loading: automatically detects and loads agents.md files.

    2.8k GitHub stars~1.1k tokensUpdated today
    Auto-check passed
  • Aggregating Performance Metrics

    jeremylongshore/tons-of-skills-marketplace

    Aggregate and centralize performance metrics from applications, systems, databases, caches, and services.

    2.8k GitHub stars~1.2k tokensUpdated today
    Auto-check passed
  • Analyzing Capacity Planning

    jeremylongshore/tons-of-skills-marketplace

    Execute this skill enables AI assistant to analyze capacity requirements and plan for future growth.

    2.8k GitHub stars~947 tokensUpdated today
    Auto-check passed
  • Analyzing Database Indexes

    jeremylongshore/tons-of-skills-marketplace

    Process use when you need to work with database indexing. An agent skill from jeremylongshore/tons-of-skills-marketplace.

    2.8k GitHub stars~2k tokensUpdated today
    Auto-check passed

Works with

Categories

Questions about Intercom Security Basics

What does Intercom Security Basics do?

Apply Intercom security best practices for tokens, webhook verification, and scopes. Intercom Security Basics is an agent skill from jeremylongshore/tons-of-skills-marketplace. Apply Intercom security best practices for tokens, webhook verification, and scopes.

When should I use Intercom Security Basics?

Intercom Security Basics fits situations like: securing access tokens; implementing webhook signature validation; configuring least-privilege OAuth scopes; with phrases like intercom security.

How do I install Intercom Security Basics in Claude Code?

Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill intercom-security-basics -a claude-code`. Or copy the skill folder (skills/.curated/intercom-security-basics in jeremylongshore/tons-of-skills-marketplace) into .claude/skills/intercom-security-basics in your project. Claude Code loads it when a task matches its description.

How do I install Intercom Security Basics in Codex?

Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill intercom-security-basics -a codex`. Or copy the skill folder (skills/.curated/intercom-security-basics in jeremylongshore/tons-of-skills-marketplace) into .agents/skills/intercom-security-basics in your project. Codex loads it when a task matches its description.

Can I use Intercom Security Basics in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill intercom-security-basics -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/intercom-security-basics, .gemini/skills/intercom-security-basics, .github/skills/intercom-security-basics and .opencode/skills/intercom-security-basics in your project.

What does Intercom Security Basics need to run?

Going by SKILL.md and its folder, Intercom Security Basics needs the command-line tools its instructions call (git, curl and jq) and credentials named INTERCOM_ACCESS_TOKEN, INTERCOM_IDENTITY_SECRET, INTERCOM_WEBHOOK_SECRET and NEW_TOKEN. Our summary lists: A credential in INTERCOM_ACCESS_TOKEN; A credential in INTERCOM_WEBHOOK_SECRET. Its frontmatter pre-approves these tools: Read, Write, Grep. Compatibility (from SKILL.md): Designed for Claude Code.

Does Intercom Security Basics access the network?

SKILL.md names 2 domains. In commands or code: api.intercom.io; the agent is likely to contact it when it follows the instructions. As links in the text: developers.intercom.com. This is read from the text; nothing was executed.

Is Intercom Security Basics safe to install?

Our automated static check of SKILL.md found notes only (mentions a .env file), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.

What licence does Intercom Security Basics use?

Intercom Security Basics is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Intercom Security Basics use?

About 1.7k tokens (SKILL.md is roughly 6.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 1.8k tokens, read only when the agent opens those files.

What are the alternatives to Intercom Security Basics?

Skills that share tags, products or a category with Intercom Security Basics: Stripe Best Practices (kanchengw/cnllm, 175 stars), Discord Php Bot Security (discord-php/DiscordPHP, 1.1k stars), GitHub OAuth Nango Integration (AgentWorkforce/relay, 867 stars) and Add OAuth Integration (rome-os/rome, 737 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Intercom Security Basics?

jeremylongshore (a GitHub user) maintains it in jeremylongshore/tons-of-skills-marketplace, which has 2,825 GitHub stars. The repository holds 3,342 skills in this directory. The repository was last updated on October 9, 2026.

Source: jeremylongshore/tons-of-skills-marketplace on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.