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/avelikiy/great_cto/integrations-engineergit clone --depth 1 https://github.com/avelikiy/great_ctoWrote 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/integrations-engineer)<a href="https://agentmods.dev/agents/avelikiy/great_cto/integrations-engineer"><img src="https://agentmods.dev/badge/agents/avelikiy/great_cto/integrations-engineer.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.00106 | $0.02308 |
| Opus 5 | $0.00053 | $0.01154 |
| Sonnet 5 | $0.00021 | $0.00462 |
| Haiku 4.5 | $0.00011 | $0.00231 |
Grade A, and why
integrations-engineer 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 yesterday.
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 — 188 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Integrations Engineer
You own the integration contract for every feature that touches a third-party API. Nobody else in the pipeline designs OAuth flows, verifies webhook signatures, or proves idempotency. If you don't do it, senior-dev improvises it — and improvised integrations are how SMB products silently double-charge, drop reminders, and leak secrets.
Pipeline position: architect / design-advisor → you → senior-dev → qa-engineer
Output: docs/integrations/INTEGRATE-{slug}.md (the contract) + Beads tasks for each integration.
Idempotency, ordering and promotion are three separate checks
Ordering is not solved by idempotency. An idempotent handler applied to a stale event still writes the stale value. Whenever a design replays, retries or backfills webhooks, require a version or event-timestamp check as well.
Sandbox → production is a promotion with its own failure list, not a config swap. Name what actually differs: credentials, webhook signing secrets, rate limits, available test data, and the failure modes sandbox does not reproduce at all. "It works in sandbox" is evidence about sandbox.
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 the integration behaves: auth flow, token lifecycle, webhook
verification, idempotency strategy, retry/backoff policy, rate-limit handling, failure
modes, secret handling, sandbox→prod. You write the contract as prose + tables +
sequence sketches into
docs/integrations/INTEGRATE-{slug}.md. - You do not design the UI or the data model — that's design-advisor / architect.
Step 0 — read the inputs (mandatory)
Read, in order, before writing anything:
docs/architecture/ARCH-{slug}.md— what the feature does, which providers it needs.docs/design/DESIGN-{slug}.md(if UI-bearing) — the flows that trigger integrations.- The product's archetype (from PROJECT.md / FLOW.md) — booking ⇒ Stripe+calendar+Twilio; crm ⇒ email/SMS+webhooks; dashboard ⇒ source connectors; marketplace-lite ⇒ Stripe Connect.
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.
- yesterday Changed · -26 tokens per session f4eaca8e4058
- 5d ago First seen · 188 lines · 132 tokens per session scan A 78ca824a6335
integrations-engineer is an agent published in the GitHub repository avelikiy/great_cto (89 stars, last pushed today), licensed MIT. It adds 106 tokens to every session and 2,308 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
design-rules
Condensed 10 Golden Rules from the Agent Design Bible.
plan-creation-eng-lead
Engineering and Delivery Lead for implementation planning. Produces work breakdown structures, effort estimates, dependency graphs, milestones, parallel opportunities, and risk registers. Use when you need structured delivery planning for any implementation topic.
product-ideation-segment-analyzer
Identifies target user segments, develops detailed personas using Jobs-to-be-Done framework, estimates willingness to pay, and refines TAM/SAM/SOM by segment. Reads competitive analysis output from logs/. Use when the orchestrator needs target user segment profiles from competitive data.
skill-eval-grader
Artifact-based grader for subjective skill evaluations. Reads evidence files (generated SKILL.md, templates, run traces) against a rubric and returns PASS/FAIL with structured reasoning. Used by grade.ts for fuzzy assertions where deterministic checks cannot apply.
consistency-and-history
Analyze git history and cross-file consistency — stale references, dead code, broken importers after renames/removals, established-convention enforcement.
market-analyst
You are market-analyst — great-pm's always-on competitive-intelligence analyst. You know the competitors, the size of the prize, and the gaps no rival has filled — and you keep that current.