What is api-connector-builder?

A guide for adding a new API integration to a codebase by following the patterns already used by its other connectors. An API connector is code that lets an application communicate with an external service.

Use it to add connectors or providers for services such as Jira or Slack while matching the repository's existing structure.

It avoids creating a second integration design and helps cover related configuration, authentication, error handling, registration, tests, and documentation.

api-connector-builder — Skill for Claude Code and Codex by fabioc-aloh

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 fabioc-aloha/Alex_Skill_Mall --skill api-connector-builder

Clone the repo

git clone --depth 1 https://github.com/fabioc-aloha/Alex_Skill_Mall

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/fabioc-aloha/alex_skill_mall/api-connector-builder/github.svg)](https://agentmods.dev/skills/fabioc-aloha/alex_skill_mall/api-connector-builder)

Your own site

<a href="https://agentmods.dev/skills/fabioc-aloha/alex_skill_mall/api-connector-builder"><img src="https://agentmods.dev/badge/skills/fabioc-aloha/alex_skill_mall/api-connector-builder/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/fabioc-aloha/alex_skill_mall/api-connector-builder"><img src="https://agentmods.dev/badge/skills/fabioc-aloha/alex_skill_mall/api-connector-builder.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 597 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.

Origin 95% copy Near-identical to another mod 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.00036	$0.00597
Opus 5	$0.00018	$0.00298
Sonnet 5	$0.00007	$0.00119
Haiku 4.5	$0.00004	$0.00060

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

Security

Grade A, and why

api-connector-builder 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.

Origin

This is a copy

95% identical to api-connector-builder — 25 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

plugins/architecture-patterns/api-connector-builder/skills/api-connector-builder/SKILL.md · 120 lines

How it starts

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

API Connector Builder

Use this when the job is to add a repo-native integration surface, not just a generic HTTP client.

The point is to match the host repository's pattern:

connector layout
config schema
auth model
error handling
test style
registration/discovery wiring

When to Use

"Build a Jira connector for this project"
"Add a Slack provider following the existing pattern"
"Create a new integration for this API"
"Build a plugin that matches the repo's connector style"

Guardrails

do not invent a new integration architecture when the repo already has one
do not start from vendor docs alone; start from existing in-repo connectors first
do not stop at transport code if the repo expects registry wiring, tests, and docs
do not cargo-cult old connectors if the repo has a newer current pattern

Workflow

1. Learn the house style

Inspect at least 2 existing connectors/providers and map:

file layout
abstraction boundaries
config model
retry / pagination conventions
registry hooks
test fixtures and naming

2. Narrow the target integration

Define only the surface the repo actually needs:

auth flow
key entities
core read/write operations
pagination and rate limits
webhook or polling model

3. Build in repo-native layers

Typical slices:

config/schema
client/transport
mapping layer
connector/provider entrypoint
registration
tests

4. Validate against the source pattern

The new connector should look obvious in the codebase, not imported from a different ecosystem.

Reference Shapes

Provider-style

providers/
  existing_provider/
    __init__.py
    provider.py
    config.py

Connector-style

integrations/
  existing/
    client.py
    models.py
    connector.py

TypeScript plugin-style

src/integrations/
  existing/
    index.ts
    client.ts
    types.ts
    test.ts

Quality Checklist

matches an existing in-repo integration pattern
config validation exists
auth and error handling are explicit
pagination/retry behavior follows repo norms
registry/discovery wiring is complete
tests mirror the host repo's style
docs/examples are updated if expected by the repo

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

6d ago First seen · 120 lines · 36 tokens per session scan A 39e8365e97f9

Subscribe to this mod's changes

api-connector-builder is a skill published in the GitHub repository fabioc-aloha/Alex_Skill_Mall (4 stars, last pushed 2d ago), licensed MIT. It adds 36 tokens to every session and 597 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 95% identical to api-connector-builder, differing in 25 lines, and is treated as a copy.

Backend and APIs agentic-ai ai-assistant ai-skills best-practices github-copilot knowledge-base

azure-storage

UTILITY SKILL — Azure Storage Services: Blob, File Shares, Queue, Table, and Data Lake. Object storage, SMB shares, async messaging, NoSQL key-value, big-data analytics. Access tiers + lifecycle management. WHEN: "blob storage", "file shares", "queue storage", "table storage", "data lake", "access tiers", "lifecycle…

jonathan-vella/apex-accelerator · 105 tokens

api-design

REST API contract designer and reviewer. ALWAYS use when designing new endpoints, reviewing existing API contracts, planning API versioning, or standardizing error models. Covers resource modeling (URL/naming), HTTP method semantics, status code selection, error model consistency, pagination/filtering/sorting…

johnqtcg/awesome-skills · 123 tokens

api-connector-builder