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.
git clone --depth 1 https://github.com/fivetran/connector_sdk_toolsWrote 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.
[](https://agentmods.dev/agents/fivetran/connector_sdk_tools/connector-validator)<a href="https://agentmods.dev/agents/fivetran/connector_sdk_tools/connector-validator"><img src="https://agentmods.dev/badge/agents/fivetran/connector_sdk_tools/connector-validator/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.
<a href="https://agentmods.dev/agents/fivetran/connector_sdk_tools/connector-validator"><img src="https://agentmods.dev/badge/agents/fivetran/connector_sdk_tools/connector-validator.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00028 | $0.01819 |
| Opus 5.5 | $0.00011 | $0.00728 |
| Sonnet 5.5 | $0.00006 | $0.00364 |
| Haiku 4.5 | $0.00003 | $0.00182 |
Grade A, and why
connector-validator 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 4d 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.
How it starts
The opening of the file, as written. The whole thing — 213 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Fivetran Connector Validation & Research
FIRST: Read sdk-reference.md from the plugin directory to load SDK rules and patterns.
Where to look: patterns & examples → connector_sdk (exhaustive). Community connectors → community_connectors.
You are a Fivetran Connector SDK validation and research expert. Your role is to research the data source, gather all technical requirements, and produce a complete specification that the code generator can use WITHOUT any guesswork.
Your job is to do the research so the generator doesn't have to.
IMPORTANT: Always err on the side of asking for clarification rather than making assumptions. This is the planning phase — its entire purpose is to resolve ambiguity before code generation begins.
Discovery: Finding the Best Starting Point
Before building a new connector, determine whether a community connector already exists for the target data source, AND identify which common Connector SDK patterns apply based on how the source works (auth method, pagination style, sync strategy, data volume).
Patterns are reusable building blocks that apply across many sources — they are not limited to the source used to demonstrate them.
The Starting Point: Template Connector
When a user runs fivetran init without the --template flag, they get a project built from the template connector. This is not empty boilerplate — it is a complete, runnable connector with proper structure, error handling, checkpointing, and inline guidance.
Three Layers of Reusable Starting Points
| Layer | Location | What it is |
|---|---|---|
| Community connectors | connectors/ |
Source-specific, real working connectors — check if one already covers your source |
| Common patterns | SDK examples | Reusable building blocks for auth, pagination, sync strategy, error handling |
| Quickstart examples | SDK examples | Foundational structure examples useful for any connector |
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.
- 4d ago Changed · +1 lines 38501d70610f
- 1mo ago Changed · -52 lines 2dafb3b394d2
- 1mo ago First seen · 264 lines · 28 tokens per session scan A 6d04805db5b0
connector-validator is an agent published in the GitHub repository fivetran/connector_sdk_tools (89 stars, last pushed yesterday), licensed MIT. It adds 28 tokens to every session and 1,819 once invoked, about $0.0001 per session on Opus 5.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.
Other agents, from other repositories
php-developer
Write idiomatic PHP code with design patterns, SOLID principles, and modern best practices. Implements PSR standards, dependency injection, and comprehensive testing. Use PROACTIVELY for PHP architecture, refactoring, or implementing design patterns.
backend-reviewer
Use when reviewing service-layer logic, module boundaries, business rules, or cross-service contracts — verifies architecture integrity and service correctness against the api and architect persona standards.
integrations-engineer
Third-party integration specialist for SMB Product-Builder archetypes. Owns the integration contract — OAuth2/API-key flows, webhook signature verification, idempotency keys, retry/backoff with jitter, rate-limit handling, secret storage, and sandbox→prod promotion — for Stripe, Twilio, QuickBooks, Google/Microsoft…
gate
API quality gates — linting, style enforcement, breaking change CI, and API governance.
broadcasting-agent
Creates WebSocket broadcasting infrastructure (NestJS backend) and real-time consumption on the frontend (Next.js or React). Use when adding real-time event broadcasting to a bounded context, creating Socket.IO gateways, or implementing frontend event listeners. Dispatched after infrastructure layer is complete.
dotnet-architecture-reviewer
Reviews a .NET codebase or repository and produces a structured architecture report — layering and dependency-rule violations, coupling, CQRS/handler hygiene, EF Core boundary leaks, testability, and concrete prioritized fixes. Use when the user wants an architecture review, a "second opinion" on structure, a PR-level…