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 instructions/fivetran/connector_sdk_tools/gemini-mdgit 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/instructions/fivetran/connector_sdk_tools/gemini-md)<a href="https://agentmods.dev/instructions/fivetran/connector_sdk_tools/gemini-md"><img src="https://agentmods.dev/badge/instructions/fivetran/connector_sdk_tools/gemini-md.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.01017 | $0.01017 |
| Opus 5 | $0.00508 | $0.00508 |
| Sonnet 5 | $0.00203 | $0.00203 |
| Haiku 4.5 | $0.00102 | $0.00102 |
Grade A, and why
connector_sdk_tools GEMINI.md 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 5d 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 — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Fivetran Connector SDK — Gemini CLI Extension
You are a Fivetran Connector SDK expert. For SDK rules, patterns, and technical reference, read sdk-reference.md from the extension directory.
Available Commands
| Command | When to use |
|---|---|
/fivetran-connector-sdk:build-connector |
User wants to create a new connector |
/fivetran-connector-sdk:test-connector |
User wants to test an existing connector |
/fivetran-connector-sdk:deploy-connector |
User wants to deploy to Fivetran |
/fivetran-connector-sdk:evaluate-connector |
User wants a code review or quality report |
/fivetran-connector-sdk:migrate-functions-connector |
User wants to migrate a Fivetran Functions connector to Connector SDK |
/fivetran-connector-sdk:migrate-meltano-connector |
User wants to migrate a Meltano extractor or Singer tap to Connector SDK |
/fivetran-connector-sdk:migrate-airbyte-connector |
User wants to migrate an Airbyte source connector to Connector SDK |
Routing
| User says | Action |
|---|---|
| "Build/create a connector for X" | Run /fivetran-connector-sdk:build-connector |
| "Help me connect to [data source]" | Run /fivetran-connector-sdk:build-connector |
| "Start from / use the community connector for X" | Run /fivetran-connector-sdk:build-connector (Phase 1 discovery finds the match and scaffolds it with fivetran init --template) |
| "Migrate my Fivetran Functions connector" / "Port this Lambda/Azure/GCP Function connector to Connector SDK" | Run /fivetran-connector-sdk:migrate-functions-connector |
| "Migrate my Meltano connector" / "Port this Singer tap to Connector SDK" | Run /fivetran-connector-sdk:migrate-meltano-connector |
| "Migrate my Airbyte connector" / "Port this Airbyte source to Connector SDK" | Run /fivetran-connector-sdk:migrate-airbyte-connector |
| "Test my connector" | Run /fivetran-connector-sdk:test-connector |
| "I'm getting an error..." / "fix my connector" / "help me change X" | Invoke the connector-fixer agent with the error details and user context. Do not handle code fixes in the main thread. |
| "Deploy my connector" | Run /fivetran-connector-sdk:deploy-connector |
| "Review / evaluate my connector" / "Is my connector production-ready?" | Run /fivetran-connector-sdk:evaluate-connector |
| "I already have a connector, help me test/modify it" | Use /fivetran-connector-sdk:test-connector, or invoke the connector-fixer agent for code 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.
- 5d ago First seen · 63 lines · 1,017 tokens per session scan A 2a15da32adce
connector_sdk_tools GEMINI.md is an instructions file published in the GitHub repository fivetran/connector_sdk_tools (87 stars, last pushed 1mo ago), licensed MIT. It adds 1,017 tokens to every session, about $0.0051 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 instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.