What is integration-development?

A development guide for connecting software to external apps such as SaaS services, internal tools, scripts, and command-line programs. It describes how authentication, connections, and actions fit together through Membrane.

Use it when building software that reads from, writes to, synchronizes with, or responds to data in another app, for one account or many users.

It explains the repeated setup needed to authenticate users and code, refresh credentials, reconnect services, and choose actions without handling each vendor's process separately.

integration-development — Skill by membranehq/agent-skills

Install

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.

Any agent

npx skills add membranehq/agent-skills --skill integration-development

Clone the repo

git clone --depth 1 https://github.com/membranehq/agent-skills

Made for: Claude Code, Codex.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/membranehq/agent-skills/integration-development/github.svg)](https://agentmods.dev/skills/membranehq/agent-skills/integration-development)

Your own site

<a href="https://agentmods.dev/skills/membranehq/agent-skills/integration-development"><img src="https://agentmods.dev/badge/skills/membranehq/agent-skills/integration-development/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/membranehq/agent-skills/integration-development"><img src="https://agentmods.dev/badge/skills/membranehq/agent-skills/integration-development.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 113 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 15,331 The whole file, excluding the scripts and references it only reads on demand.

Security scan C 2 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00113	$0.15331
Opus 5.5	$0.00045	$0.06132
Sonnet 5.5	$0.00023	$0.03066
Haiku 4.5	$0.00011	$0.01533

Measured 2mo ago against content hash d2ab16280933, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade C, and why

integration-development scanned grade C with 2 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 2mo 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.

Hidden instructionshighPrompt injection

Directives inside HTML comments, invisible characters or bidirectional overrides are read by the model and not by the person reviewing the file.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

curl -X POST $API/integrations -H "Authorization: Bearer $TOKEN" -H "Content-Type: application/json" \

skills/integration-development/SKILL.md · 1,819 lines

How it starts

The opening of the file, as written. The whole thing — 1,819 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Integration Development

How integrations work — the five-step mental model

Every Membrane-backed feature walks through the same linear spine. Steps 0–3 are the core path; step 4 is a capability upgrade you graduate into when your app isn't bound to one specific vendor.

Step 0: Authenticate yourself   — you, the developer; via MCP or `membrane` CLI
Step 1: Authenticate your code  — sign JWTs in your backend
                                  ↳ single-tenant vs multi-tenant decided HERE
Step 2: Create connections      — `membrane.ui.connect()` in your app UI
Step 3: Use connections         — call actions on the external app
                                  ↳ discover via intent search when you don't know what to call
                                  ↳ dispatch: inline api/code | catalog id | workspace key
Step 4 (advanced): Universal    — app-agnostic code via universal actions + cross-connection logic

In an MCP session step 0 is already done — membrane status confirms.

The most consequential choice — whether your app serves one shared external account (single-tenant: a team CRM, an internal Slack) or many end users (multi-tenant: each user connects their own Gmail, Linear, etc.) — lives in step 1. It determines what your backend puts in the JWT it signs, which in turn scopes every connection and action that follows. Everything downstream of step 1 is uniform: the same membrane.ui.connect() call, the same /act dispatch.

Before you code — typical discovery flow

Four commands cover most starting points:

# 1. Populate env with real credentials.
membrane credentials --shell > .env.local

# 2. Find the app you're integrating with (returns externalAppId).
membrane external-app list --search <app-name>

# 3. List catalog actions for that app.
membrane action list --externalAppId <id>

# 4. Check existing connections in the current tenant.
membrane connection list

CLI quick reference.

Mint a JWT: membrane token (add --tenantKey <key> for per-user, --manager for POST /actions and other manager ops).

membrane --help or membrane <command> --help lists the full surface.

Read the full file on GitHub · 1,819 lines

Changes

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.

2mo ago First seen · 1,819 lines · 113 tokens per session scan C d2ab16280933

Subscribe to this mod's changes

integration-development is a skill published in the GitHub repository membranehq/agent-skills (5 stars, last pushed 2d ago), licensed MIT. It adds 113 tokens to every session and 15,331 once invoked, about $0.0005 per session on Opus 5.5. A static security scan graded it C with 2 findings (hidden instructions, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Backend and APIs

integration-development next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
integration-developmentmembranehq/agent-skills	Skill	5	2d ago	MIT	C	113	Claude Code, Codex
mem0-oss-to-platformmem0ai/mem0	Skill	69k	5d ago	Apache-2.0	A	217	Claude Code, Codex
azure-mgmt-botservice-dotnetmicrosoft/skills	Skill	3.2k	today	MIT	A	78	Claude Code
fastapi-router-pymicrosoft/skills	Skill	3.2k	today	MIT	A	46	Claude Code
api-designericrisco/rsc-harness	Skill	590	today	MIT	A	105	Claude Code, Codex
migrate-segw-to-raparc-mcp/arc-1	Skill	260	today	MIT	A	106	Claude Code
telnyx-messaging-hosted-curlteam-telnyx/ai	Skill	226	today	MIT	A	45	Claude Code

integration-development