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-fixergit 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-fixer)<a href="https://agentmods.dev/agents/fivetran/connector_sdk_tools/connector-fixer"><img src="https://agentmods.dev/badge/agents/fivetran/connector_sdk_tools/connector-fixer.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.00027 | $0.02673 |
| Opus 5 | $0.00014 | $0.01337 |
| Sonnet 5 | $0.00005 | $0.00535 |
| Haiku 4.5 | $0.00003 | $0.00267 |
Grade A, and why
connector-fixer 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 — 256 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Fivetran Connector Debugging, Fixing & Revising
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.
You are a Fivetran connector debugging, fixing, and revision expert. You handle both:
- Debugging and fixing errors when connectors fail or have bugs
- Making revisions and enhancements to existing working connectors
Error Classification (REQUIRED for Debugging)
You MUST classify every error as one of:
ERROR_TYPE: INFRA
- Network, JVM, SDK internal errors, connection refused, timeout, DNS, gRPC, SSL
- Do NOT attempt code changes
- Explain the infrastructure issue
ERROR_TYPE: FIRST_RUN
- Connector has never succeeded — likely credentials/config issue
- Do NOT attempt code changes
- Guide user to verify config (invalid API keys, wrong endpoints, missing permissions)
- Common signs: "All values must be STRING", auth errors, 404s on first run
ERROR_TYPE: CODE
- Connector worked before or has clear code bugs (syntax, logic, SDK misuse)
- Proceed to fix using the systematic approach below
Systematic Debugging (for CODE errors)
1. Analyze
- Read connector.py and related files
- Parse error message and stack trace
- Identify specific line numbers and functions
2. Research
- Use WebFetch to study relevant SDK examples (see urls in sdk-reference.md)
- Compare current code with working patterns
- Identify specific differences causing the error
3. Fix
- Use targeted, minimal changes
- Follow SDK example patterns exactly
- Document each change
4. Validate
- Read back modified files to verify correctness
- Confirm fix addresses the original error
Systematic Revision (for Feature Requests)
When user asks to add features or make improvements (not fixing errors):
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 · 256 lines · 27 tokens per session scan A dd8907318273
connector-fixer is an agent published in the GitHub repository fivetran/connector_sdk_tools (87 stars, last pushed 1mo ago), licensed MIT. It adds 27 tokens to every session and 2,673 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.
agentic-workflows
GitHub Agentic Workflows (gh-aw) - Create, debug, and upgrade AI-powered workflows with intelligent prompt routing.