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/commands/fivetran/connector_sdk_tools/evaluate-connector)<a href="https://agentmods.dev/commands/fivetran/connector_sdk_tools/evaluate-connector"><img src="https://agentmods.dev/badge/commands/fivetran/connector_sdk_tools/evaluate-connector/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/commands/fivetran/connector_sdk_tools/evaluate-connector"><img src="https://agentmods.dev/badge/commands/fivetran/connector_sdk_tools/evaluate-connector.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.00017 | $0.00093 |
| Opus 5.5 | $0.00007 | $0.00037 |
| Sonnet 5.5 | $0.00003 | $0.00019 |
| Haiku 4.5 | $0.00002 | $0.00009 |
Grade A, and why
evaluate-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 1mo 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.
What it actually says
Invoke the evaluate-connector skill from this plugin to perform a static code review of the connector. The skill checks for SDK compliance violations, security issues, data reliability problems, and code quality, then produces a scored report.
User request: $ARGUMENTS
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.
- 1mo ago First seen · 9 lines · 17 tokens per session scan A 1e213d64a599
evaluate-connector is a command published in the GitHub repository fivetran/connector_sdk_tools (89 stars, last pushed yesterday), licensed MIT. It adds 17 tokens to every session and 93 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 commands, from other repositories
document
On-demand documentation generation — API docs, architecture updates, user guides.
review-rust
Focused Rust/Tauri backend review with rust-backend-architect (Primary Owner).
connector-review
Review DataHub connector code for standards compliance and quality.
api-style-review
Review SAP API style compliance for REST, OData, OpenAPI, SDK naming, documentation, and lifecycle readiness.
api-review
Review the current code or API against API design principles — identifies violations and suggests improvements.
check-syncro-apis
Diff Syncro's live OpenAPI spec against this repo's cached docs/swagger.json and report any new endpoints, query params, or request-body fields that the MCP server doesn't yet expose.