deploy-connector

deploy-connector is a skill for Claude Code, Codex from fivetran/connector_sdk_tools. It costs 31 tokens per session (1,390 once invoked), scanned A, original, MIT.

A deployment workflow for a Fivetran connector, which copies data from an external service into a database or warehouse.

In plain words
What is it for?
Use it to validate, test, package, and deploy a connector from the current project directory.
Why use it?
It checks the required files and connector structure before packaging and sending the connector to Fivetran.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: mentions subagents.

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/fivetran/connector_sdk_tools/deploy-connector
Any agent
npx skills add fivetran/connector_sdk_tools --skill deploy-connector
Clone the repo
git clone --depth 1 https://github.com/fivetran/connector_sdk_tools

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.

agentmods badge for deploy-connector

README.md
[![agentmods](https://agentmods.dev/badge/skills/fivetran/connector_sdk_tools/deploy-connector.svg)](https://agentmods.dev/skills/fivetran/connector_sdk_tools/deploy-connector)
Your own site
<a href="https://agentmods.dev/skills/fivetran/connector_sdk_tools/deploy-connector"><img src="https://agentmods.dev/badge/skills/fivetran/connector_sdk_tools/deploy-connector.svg" alt="Measured on agentmods" height="20"></a>
Per session 31 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,390 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. 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.00031 $0.01390
Opus 5 $0.00015 $0.00695
Sonnet 5 $0.00006 $0.00278
Haiku 4.5 $0.00003 $0.00139

Measured 6d ago against content hash cc3e52caecd4, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-05, from the pricing page.

Security

Grade A, and why

deploy-connector 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 6d 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.

canonical/skills/deploy-connector/SKILL.md · 121 lines

How it starts

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

Context: This plugin is for the Fivetran Connector SDK (CSDK). "CSDK" is shorthand for "Connector SDK".

Deploy Fivetran Connector

FIRST: Read sdk-reference.md from the plugin directory to load SDK rules and patterns.

Package and deploy the connector in the current directory.

Step 1: Pre-Deployment Validation

Verify the connector is ready:

  1. Files exist: connector.py, configuration.json, requirements.txt, README.md
  2. Code quality: Read connector.py and check for:
    • Both schema() and update() functions present
    • connector = Connector(update=update, schema=schema) in global scope
    • if __name__ == "__main__": connector.debug() entry point
    • No forbidden patterns (Dict[str, Any], Generator[op.Operation, ...], op.Operation in type hints)
  3. Configuration: configuration.json is JSON. enter_configuration.py encrypts every field by default using inline ENCRYPTED:v1:<key_id>:local-fernet: values, but user-chosen plaintext values are also accepted. Do not read, print, copy, or deploy plaintext configuration values in chat.

Step 2: Run Final Test

Use the secure runner:

python <plugin>/tools/run_connector.py <connector_directory>

If the test fails, classify the error (INFRA / FIRST_RUN / CODE) and — for CODE errors — apply the fixer workflow (see workflows/fixer.md in the plugin, or — in plugins that support subagents — invoke the connector-fixer subagent).

Step 3: Deploy

The deploy tool auto-discovers the destination via the Fivetran REST API — you only need to run:

python <plugin>/tools/deploy_connector.py <connector_directory>

The tool:

  1. Reads FIVETRAN_API_KEY from the environment.
  2. Calls GET /v1/groups to discover the destination (group) name, picking the single one automatically or prompting if more than one exists.
  3. Derives the connection name from the connector directory name (sanitized to Fivetran rules). To set it explicitly, pass --connection <name> (must begin with _ or a lowercase letter; only _, lowercase, digits).
  4. Invokes fivetran deploy --destination <name> --connection <name> --force with the runtime configuration passed via named pipe after decrypting configuration values in memory. --force auto-answers the overwrite prompts so redeploys don't hang.
  5. Captures and prints the Connection ID from the deploy log.

Read the full file on GitHub · 121 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. 6d ago First seen · 121 lines · 31 tokens per session scan A cc3e52caecd4

Subscribe to this mod's changes

deploy-connector is a skill published in the GitHub repository fivetran/connector_sdk_tools (87 stars, last pushed 1mo ago), licensed MIT. It adds 31 tokens to every session and 1,390 once invoked, about $0.0002 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-30.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

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…

vercel/next.js · 95 tokens

next-partial-prefetching-adoption

Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…

vercel/next.js · 103 tokens

chronicle

Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…

microsoft/vscode · 72 tokens

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…

openai/codex · 113 tokens