build-connector

build-connector is a skill for Claude Code from getomnico/omni. It costs 41 tokens per session (5,890 once invoked), scanned A, original, Apache-2.0.

A guide for building connectors for Omni, an open-source workplace AI platform. A connector is a separately packaged bridge that imports data from another service and exposes approved actions, tools, resources, or prompts to agents.

In plain words
What is it for?
Use it to scaffold a connector, choose Python, TypeScript, or Rust, add OAuth scopes and read/write actions, implement scheduled or realtime synchronization, and define document IDs and checkpoints.
Why use it?
It gives a clear structure for handling provider data, credentials, permissions, synchronization, and stable contracts between connectors and agents. It is intended for a monorepo, a code repository containing multiple related projects, with local SDK dependencies.

Skill for Claude Code

Written for Claude Code: user-invocable in frontmatter.

Good fit Use it to scaffold a connector, choose Python, TypeScript, or Rust, add OAuth scopes and read/write actions, implement scheduled or realtime synchronization, and define document IDs and checkpoints.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/getomnico/omni/build-connector
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 getomnico/omni --skill build-connector
Clone the repo
git clone --depth 1 https://github.com/getomnico/omni

Made for: Claude Code.

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 build-connector

README.md
[![agentmods](https://agentmods.dev/badge/skills/getomnico/omni/build-connector/github.svg)](https://agentmods.dev/skills/getomnico/omni/build-connector)
Your own site
<a href="https://agentmods.dev/skills/getomnico/omni/build-connector"><img src="https://agentmods.dev/badge/skills/getomnico/omni/build-connector/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.

agentmods 80×15 button for build-connector

Your own site · 80×15
<a href="https://agentmods.dev/skills/getomnico/omni/build-connector"><img src="https://agentmods.dev/badge/skills/getomnico/omni/build-connector.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 41 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 5,890 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
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.00041 $0.05890
Opus 5 $0.00020 $0.02945
Sonnet 5 $0.00008 $0.01178
Haiku 4.5 $0.00004 $0.00589

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

Security

Grade A, and why

build-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 10d 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.

.claude/skills/build-connector/SKILL.md · 411 lines

How it starts

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

You are helping build a connector for Omni, an open-source AI agent platform for the workplace. Connectors are lightweight bridges between Omni and third-party systems: they sync workplace data into Omni's index and expose safe actions, MCP tools, resources, and prompts that workplace agents can use.

Core Principles

  • One container per connector. Independently packaged and deployed.
  • Connectors never interact directly with Omni services. Everything goes through connector-manager via the SDK.
  • SDKs are local dependencies in this monorepo, not published package registries.
  • Python, TypeScript, and Rust are first-class. Pick the language that best fits the provider SDK/ecosystem.
  • Agents depend on connector contracts. Model read/write actions, permissions, OAuth scopes, resources, prompts, and document IDs carefully.

Scheduled sync flow: connector-manager creates a sync run -> sends POST /sync to the connector -> connector fetches source config/credentials through the SDK -> connector fetches provider data -> stores/extracts content via SDK -> emits events -> checkpoints as it advances -> completes or fails through SDK.

Realtime sync flow: connector-manager starts/monitors a long-running realtime sync when the manifest declares support -> connector keeps a webhook/socket/watcher alive, heartbeats while idle, and emits repair/update events or creates short follow-up sync runs as needed.

Checklist

Every new built-in connector usually requires changes across these areas:

  1. Connector implementation — sync logic, provider client, config/credential types, manifest, actions/tools/resources.
  2. Database migration — add source type to sources_source_type_check; add service provider to service_credentials_provider_check if new.
  3. Rust SourceType enum — add variant in shared/src/models.rs even for Python/TS connectors, because connector-manager is Rust.
  4. FrontendSourceType, ServiceProvider if new, icon, setup dialog, integrations page, sync interval defaults.
  5. Docker Compose — service definition, dev override, port in .env.example, ENABLED_CONNECTORS comment.
  6. Terraform — AWS ECS task/service and GCP Cloud Run service.
  7. GitHub Actions — path filter, build job, release matrix entry.
  8. Integration tests — mock provider API, connector-manager/testcontainer harness, sync/action assertions.

Read the full file on GitHub · 411 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. 10d ago First seen · 411 lines · 41 tokens per session scan A c9b7e27bf9ab

Subscribe to this mod's changes

build-connector is a skill published in the GitHub repository getomnico/omni (773 stars, last pushed today), licensed Apache-2.0. It adds 41 tokens to every session and 5,890 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

mem0-oss-to-platform

Plan and then execute a migration of a project from the mem0 open-source / self-hosted SDK (the local Memory class) to the mem0 Platform / hosted / managed SDK (the MemoryClient class). Use this whenever a developer wants to move, switch, or migrate their mem0 usage off OSS/self-hosted to the hosted API — e.g.…

mem0ai/mem0 · 273 tokens

agui-dotnet-protobuf

Use the protobuf wire transport (instead of the default Server-Sent Events) for an AG-UI connection with the AG-UI .NET SDK — a compact binary event stream negotiated via the Accept header. USE FOR: making an AGUIChatClient prefer protobuf by wiring an AGUIEventStreamHandler with ProtobufEventStreamFormatter (then…

ag-ui-protocol/ag-ui · 162 tokens

azure-mgmt-botservice-dotnet

Azure Resource Manager SDK for Bot Service in .NET. Management plane operations for creating and managing Azure Bot resources, channels (Teams, DirectLine, Slack), and connection settings. Triggers: "Bot Service", "BotResource", "Azure Bot", "DirectLine channel", "Teams channel", "bot management .NET", "create bot".

microsoft/skills · 78 tokens

fastapi-router-py

Create FastAPI routers with CRUD operations, authentication dependencies, and proper response models. Use when building REST API endpoints, creating new routes, implementing CRUD operations, or adding authenticated endpoints in FastAPI applications.

microsoft/skills · 46 tokens

migrate-segw-to-rap

Reverse-engineer a SEGW-built OData V2 service (MPC/DPC/MPCEXT/DPCEXT) into a modern RAP V4 service — tables, CDS views (interface + projection), behavior definitions, draft entities, service definition + binding. Use when asked to "migrate this SEGW service to RAP", "convert OData V2 to V4 RAP", "modernize this…

arc-mcp/arc-1 · 106 tokens

telnyx-messaging-hosted-curl

Set up hosted SMS numbers, toll-free verification, and RCS messaging. Use when migrating numbers or enabling rich messaging features. This skill provides REST API (curl) examples.

team-telnyx/ai · 45 tokens