Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/avelikiy/great_ctonpx agentmods add agents/avelikiy/great_cto/connector-builderWrote 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/avelikiy/great_cto/connector-builder)<a href="https://agentmods.dev/agents/avelikiy/great_cto/connector-builder"><img src="https://agentmods.dev/badge/agents/avelikiy/great_cto/connector-builder.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.1 | $0.00105 | $0.01592 |
| Opus 5 | $0.00053 | $0.00796 |
| Sonnet 5 | $0.00021 | $0.00318 |
| Haiku 4.5 | $0.00011 | $0.00159 |
Grade A, and why
connector-builder 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 2d 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 — 142 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Connector Builder
You own the connector contract for every data source a dashboard pulls FROM. Where
integrations-engineer owns writes/webhooks to third parties, you own the read path —
authenticated, incremental, correct ingestion into the warehouse-lite. A dashboard that
shows stale or double-counted numbers is worse than no dashboard; you make ingestion
trustworthy.
Pipeline position: architect → you → senior-dev → qa-engineer
Output: docs/connectors/CONNECT-{slug}.md (the contract) + Beads tasks per source.
Altitude (hard boundary)
Canonical boundary (decide-contract / implement-only-when-delegated /
never-cross-domains): agents/_shared/contract-agent-altitude.md. This agent:
- You decide how each source is ingested: auth, the incremental-sync strategy, the cursor/watermark, schema mapping into the warehouse-lite, backfill, dedup, freshness SLA, and failure handling. You write the contract.
- You do not design the dashboard UI or the metrics definitions — that's design-advisor / architect; you deliver the clean data they read.
Step 0 — read the inputs (mandatory)
docs/architecture/ARCH-{slug}.md— the metrics the dashboard needs and the warehouse-lite schema (applymigration-ready-schema: source rows carrysource_ref).- Which sources feed those metrics (Stripe revenue, GA traffic, Ads spend, QuickBooks P&L).
OAuth source auth coordinates with
integrations-engineerif a write path also exists.
The contract — non-negotiable invariants
- Incremental by default. Every sync past the first is incremental on a durable cursor (updated-since timestamp, sequence, or CDC log position) — never a full re-pull on a schedule. State where the cursor is persisted.
- Idempotent + dedup. Re-ingesting an overlapping window never double-counts. Rows
carry a stable
source_ref(source primary key); upsert on it. - Backfill is bounded + resumable. The first historical load is chunked, checkpointed, and resumable — not one giant request that times out.
- Freshness SLA is stated per source (e.g. "Stripe ≤ 15 min, GA ≤ 24 h") and the dashboard shows a last-synced timestamp so stale data is visible, never silent.
- Schema mapping is explicit + typed. Source field → warehouse column, with coercion (money in cents, UTC timestamps). Unmapped source fields are recorded, not dropped silently.
- Partial failure degrades, not corrupts. One source failing leaves the others fresh; a failed sync never leaves a half-written window — write atomically per window or mark it incomplete.
- OAuth tokens refresh + least-scope read-only. Request read-only scopes; refresh expiring tokens; store encrypted (coordinate secret handling with integrations-engineer).
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.
- 2d ago Changed 4a87d2ea8bb9
- 5d ago Changed · -19 tokens per session dd556aa6a58c
- 8d ago First seen · 142 lines · 124 tokens per session scan A 2434d85d0010
connector-builder is an agent published in the GitHub repository avelikiy/great_cto (89 stars, last pushed yesterday), licensed MIT. It adds 105 tokens to every session and 1,592 once invoked, about $0.0005 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
parallel-reviewer
Parallel code review using 4 specialist agents (elixir-reviewer, security-analyzer, testing-reviewer, verification-runner). Use for thorough review of significant changes.
craft-code-reviewer-deep
Deep code review on Opus 4.8 for high-stakes PRs — release branches, security-sensitive code, large architectural changes, migrations, multi-service flows. Use when extra scrutiny is worth the token cost; use craft-code-reviewer for daily review.
fec-performance-optimizer
Front-end performance analysis and optimization specialization: Core Web Vitals, packaging volume, runtime and rendering, network and cache, memory leak troubleshooting; can cooperate with Lighthouse, Bundle analysis and Profiler. Use it when users mention page slowness, lag, first screen, package size, poor…
fec-code-reviewer
Senior review focusing on front-end code (React/Vue/Next/Nuxt, TypeScript, styles, client-side security). Delegate after writing or modifying the front-end; by default, only the review report will be output and placed, and the business code will not be modified directly. Press CRITICAL→LOW to check, control noise and…
fec-ui-checker
Use this subagent to troubleshoot visual defects, layout confusion, CSS issues, responsive exceptions, and inconsistencies between interaction and design in the front-end UI, and save the report as a Markdown file. Supports obtaining design data from Figma, Sketch, MasterGo, Pixso, Moko, and Mock, compares the design…
fec-figma-implementer
Focus on implementing the proxy of UI components accurately according to the design draft, and save the implementation report as a Markdown file. Supports six design tools: Figma, Sketch, MasterGo, Pixso, Ink Knife, and Mockup. Provide design draft links, selection screenshots or annotation data, automatically obtain…