apideck-migration

apideck-migration is a skill for Claude Code from apideck-libraries/api-skills. It costs 65 tokens per session (2,579 once invoked), scanned B, original, Apache-2.0.

A migration guide for replacing separate integrations to services such as Salesforce, HubSpot, and QuickBooks with Apideck's single unified API. An API integration is code that lets one application exchange data with another.

In plain words
What is it for?
Use it to inventory current integrations, check which operations Apideck supports, preserve service-specific fields, and move the work over in stages.
Why use it?
It helps plan the change without losing existing data flows or deleting working integration code before the replacement is verified.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the apideck plugin — 181 skills, 3 commands shipped together

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.

agentmods
npx agentmods add skills/apideck-libraries/api-skills/apideck-migration
Any agent
npx skills add apideck-libraries/api-skills --skill apideck-migration
Clone the repo
git clone --depth 1 https://github.com/apideck-libraries/api-skills

Made for: Claude Code.

Or install apideck, the plugin that ships this one along with the rest of its 181 skills, 3 commands.

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.

agentmods badge for apideck-migration

README.md
[![agentmods](https://agentmods.dev/badge/skills/apideck-libraries/api-skills/apideck-migration.svg)](https://agentmods.dev/skills/apideck-libraries/api-skills/apideck-migration)
Your own site
<a href="https://agentmods.dev/skills/apideck-libraries/api-skills/apideck-migration"><img src="https://agentmods.dev/badge/skills/apideck-libraries/api-skills/apideck-migration.svg" alt="Measured on agentmods" height="20"></a>
Per session 65 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,579 The whole file, excluding the scripts and references it only reads on demand.
Security scan B 1 finding. Scan, not verified.
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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00065 $0.02579
Opus 5 $0.00032 $0.01290
Sonnet 5 $0.00013 $0.00516
Haiku 4.5 $0.00006 $0.00258

Measured 5d ago against content hash 1d1cd465c2f7, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade B, and why

apideck-migration 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 5d 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.

Sends data to an external URLmediumData exfiltration

A POST to an outside endpoint may be telemetry or may be exfiltration; either way the mod talks to somewhere, and you should know where.

const response = await fetch("https://unify.apideck.com/proxy", { method: "POST",
providers/claude/plugin/skills/apideck-migration/SKILL.md · 263 lines

How it starts

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

Apideck Migration Guide Skill

Overview

This skill helps migrate existing direct third-party API integrations (Salesforce, HubSpot, QuickBooks, Xero, etc.) to Apideck's unified API layer. The benefit is replacing N separate integrations with a single Apideck integration that supports 200+ connectors.

IMPORTANT RULES

  • ALWAYS check connector coverage before migrating. Not all operations may be supported through the unified API.
  • ALWAYS preserve existing data flows and business logic. Migration should be transparent to end-users.
  • USE pass_through for connector-specific fields that don't map to the unified model.
  • USE custom field mapping in Vault for recurring connector-specific fields.
  • NEVER delete the existing integration code until the Apideck migration is verified in production.
  • RECOMMEND a phased migration: start with read operations, then writes, then webhooks.

Migration Strategy

Phase 1: Assessment

  1. Inventory existing integrations — List all third-party APIs currently in use
  2. Map operations — For each integration, list the CRUD operations and fields used
  3. Check coverage — Verify each operation is supported via the Apideck Connector API
  4. Identify gaps — Note operations that need pass_through or Proxy API
  5. Plan consumer mapping — Decide how your users/tenants map to Apideck consumer IDs

Phase 2: Connection Setup

  1. Create Apideck account — Get API key and App ID from the dashboard
  2. Enable connectors — Enable the connectors you need in the Apideck dashboard
  3. Integrate Vault — Add Vault JS to your frontend for user-managed connections
  4. Create consumers — Map your existing users to Apideck consumer IDs
  5. Authorize connections — Have users re-authorize via Vault (OAuth is handled automatically)

Phase 3: Read Migration (Low Risk)

Replace read operations first since they're non-destructive:

// BEFORE: Direct Salesforce API
const contacts = await salesforce.sobjects.Contact.find({
  Email: "[email protected]",
});

// AFTER: Apideck Unified API
const { data } = await apideck.crm.contacts.list({
  serviceId: "salesforce",
  filter: { email: "[email protected]" },
});

Read the full file on GitHub · 263 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.

  1. 5d ago First seen · 263 lines · 65 tokens per session scan B 1d1cd465c2f7

Subscribe to this mod's changes

apideck-migration is a skill published in the GitHub repository apideck-libraries/api-skills (3 stars, last pushed 6d ago), licensed Apache-2.0. It adds 65 tokens to every session and 2,579 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it B with 1 finding (sends data to an external url). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other skills, from other repositories

extract-design

Extract a complete design system — colors, typography, spacing, components, shadows, and W3C design tokens — from any live website using Dembrandt. Runs a headless browser against the URL and returns real computed values from the DOM. Use when you need a site's actual design tokens, want to reverse-engineer a visual…

dembrandt/dembrandt-skills · 82 tokens

data-display-and-selection

Complex data deserves multiple view modes — grid, list, table — chosen by the user based on their task. Row and item selection should use large hit areas (the whole row or card, not just a checkbox). Selected state is communicated through a subtle background colour shift. Mass actions appear when items are selected.…

dembrandt/dembrandt-skills · 85 tokens

generate-ui-from-brand

Pipeline skill — turns a URL or DESIGN.md into a concrete UI structure with decisions already made. Extracts live design tokens, normalizes them into a semantic system, applies UX principles, and outputs an actionable UI spec. Use when building UI for an existing brand from scratch, auditing a design system, or…

dembrandt/dembrandt-skills · 72 tokens

information-architecture

In large applications, information architecture determines whether users can find, understand, and act on data. Naming matters. The UI should mirror the data model and signal how data can be transformed. Dangerous or irreversible changes always require a confirm dialog. Use when designing navigation, naming entities…

dembrandt/dembrandt-skills · 71 tokens

visual-emphasis-and-hierarchy

The most important actions and content in a UI should be visually prominent — through size, colour, weight, and position. Visual hierarchy guides the user's eye to what matters most and signals which action is primary. Use when designing button groups, CTAs, dashboards, cards, or any layout where actions or content…

dembrandt/dembrandt-skills · 73 tokens

domain-expert-configuration

Configuration UIs for domain experts — users who understand their field deeply but are not software developers — require domain language, sensible defaults, and grouping by professional concept rather than technical parameter. Use when designing settings panels, solver or algorithm configuration, constraint editors…

dembrandt/dembrandt-skills · 77 tokens