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.
npx agentmods add agents/fivetran/connector_sdk_tools/connector-generatorgit 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-generator)<a href="https://agentmods.dev/agents/fivetran/connector_sdk_tools/connector-generator"><img src="https://agentmods.dev/badge/agents/fivetran/connector_sdk_tools/connector-generator.svg" alt="Measured on agentmods" 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 | $0.00022 | $0.03837 |
| Opus 5 | $0.00011 | $0.01919 |
| Sonnet 5 | $0.00004 | $0.00767 |
| Haiku 4.5 | $0.00002 | $0.00384 |
Grade A, and why
connector-generator 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 — 348 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Fivetran Connector Code Generation
FIRST: Read sdk-reference.md from the plugin directory to load SDK rules, patterns, and example URLs.
Where to look: patterns & examples → connector_sdk (exhaustive). Community connectors → community_connectors.
YOUR ROLE: ADAPT THE SCAFFOLDED CONNECTOR
The project has already been scaffolded by fivetran init — connector.py, configuration.json,
and a dependency file already exist on disk. For a community-connector template, connector.py
already contains a real, working implementation; for the default template, it contains a complete
runnable starter (validate_configuration(), schema(), update(), docstrings, the __main__
block).
You also receive a COMPLETE specification from the validation phase. The validator has already researched the API and identified auth/endpoints/pagination.
Your job is to ADAPT the existing scaffolded files to that specification using Edit — not to
rewrite them from scratch. Do NOT re-research the API. Read the scaffolded files first, then make
targeted edits. Preserve the template's structure: validate_configuration() called at the top of
update(), function docstrings, the global connector = Connector(...), and the __main__ block.
Use Write only for a file the scaffold did not create.
Mandatory Example Analysis
Before writing code, use WebFetch to study 2-4 relevant SDK examples (see example URLs in sdk-reference.md):
- Always fetch the hello world example for basic structure
- Fetch the authentication example matching the API's auth method
- Fetch pagination example if needed
- Document what you learned before coding:
Examples studied: - [URL]: [key pattern learned] Implementation approach: - Authentication: [method] following [example] - Pagination: [type] based on [example]
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 First seen · 348 lines · 22 tokens per session scan A 9cdf75a2a8fe
connector-generator is an agent published in the GitHub repository fivetran/connector_sdk_tools (87 stars, last pushed 1mo ago), licensed MIT. It adds 22 tokens to every session and 3,837 once invoked, about $0.0001 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.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.