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 skills add fivetran/connector_sdk_tools --skill test-connectorgit 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/skills/fivetran/connector_sdk_tools/test-connector)<a href="https://agentmods.dev/skills/fivetran/connector_sdk_tools/test-connector"><img src="https://agentmods.dev/badge/skills/fivetran/connector_sdk_tools/test-connector.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 52 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
- medium Excessive Agency · line 53 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.01558 |
| Opus 5 | $0.00018 | $0.00779 |
| Sonnet 5 | $0.00007 | $0.00312 |
| Haiku 4.5 | $0.00004 | $0.00156 |
Grade A, and why
test-connector 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 8d 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 — 168 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Context: This plugin is for the Fivetran Connector SDK (CSDK). "CSDK" is shorthand for "Connector SDK".
Test Connector
FIRST: Read sdk-reference.md from the plugin directory to load SDK rules and patterns.
Test the connector specified by the user.
If no connector name is provided:
Ask which connector to test. List any directories in the workspace that contain a connector.py file as options.
Example: "Which connector would you like to test? I found: github_connector, stripe_connector"
Step 1: Verify Project Files
Check that required files exist in the connector directory:
connector.py— main implementationconfiguration.json— connector settings with encrypted field valuesrequirements.txt— dependencies
If any are missing, inform the user and stop.
Step 2: Setup Environment (only if needed)
Skip if .venv already exists.
macOS/Linux:
uv venv .venv
uv pip install --python .venv/bin/python -r requirements.txt fivetran_connector_sdk
Windows PowerShell:
uv venv .venv
uv pip install --python .\.venv\Scripts\python.exe -r requirements.txt fivetran_connector_sdk
Step 3: Credential Gate
Do not manually inspect values in configuration.json. The secure runner is the configuration loader.
HARD RULES — violating any of these is a failure:
- DO NOT use
AskUserQuestion(or any checkbox / choice-menu / multi-option UI) to ask how the user wants to enter credentials. There is exactly one way. - DO NOT present "Tell me the values to use" or any chat-based credential-entry choice.
- DO NOT ask the user to paste configuration values in chat.
- DO NOT ask the user to show you fields from
configuration.json. - DO NOT run
enter_configuration.pyyourself. The user must run it in their own separate terminal. - DO NOT print, quote, summarize, or expose values from
configuration.json. - DO NOT ask any credential-related question before running the secure runner.
Run the secure runner immediately:
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.
- 8d ago First seen · 168 lines · 36 tokens per session scan A b5612d8d22aa
test-connector is a skill published in the GitHub repository fivetran/connector_sdk_tools (87 stars, last pushed 2mo ago), licensed MIT. It adds 36 tokens to every session and 1,558 once invoked, about $0.0002 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 skills, from other repositories
cli-eval
Create and run evaluation suites, watch live benchmark progress, view scorecards, compare model performance, and integrate eval runs with CI workflows from the CLI.
model-merging
Merge multiple fine-tuned models using mergekit to combine capabilities without retraining. Use when creating specialized models by blending domain-specific expertise (math + coding + chat), improving performance beyond single models, or experimenting rapidly with model variants. Covers SLERP, TIES-Merging, DARE, Task…
darwinian-evolver
Evolve prompts/regex/SQL/code with Imbue's evolution loop.
validate
Validate Semantica pipelines, extraction quality, graph schemas, and ontology consistency. Returns structured error/warning checklists. Uses PipelineValidator, PipelineBuilder.validatepipeline(), GraphValidator, and OntologyValidator. Sub-commands: pipeline, step, dependencies, extraction, graph, ontology, performance.
launching-evals
Run, monitor, analyze, and debug LLM evaluations via nemo-evaluator-launcher. Covers running evaluations, checking status and live progress, debugging failed runs, exporting artifacts and logs, and analyzing results. ALWAYS triggers on mentions of running evaluations, checking progress, debugging failed evals…
nemo-automodel-recipe-development
Create and modify NeMo AutoModel training and evaluation recipes, including YAML structure, builders, and execution flow.