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 kombohq/company-brain --skill setup-connectorgit clone --depth 1 https://github.com/kombohq/company-brainWrote 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/kombohq/company-brain/setup-connector)<a href="https://agentmods.dev/skills/kombohq/company-brain/setup-connector"><img src="https://agentmods.dev/badge/skills/kombohq/company-brain/setup-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/skills/kombohq/company-brain/setup-connector"><img src="https://agentmods.dev/badge/skills/kombohq/company-brain/setup-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.00063 | $0.01424 |
| Opus 5.5 | $0.00025 | $0.00570 |
| Sonnet 5.5 | $0.00013 | $0.00285 |
| Haiku 4.5 | $0.00006 | $0.00142 |
Grade A, and why
setup-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 2mo 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 — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Set up an existing connector
This skill covers enabling a connector that already exists in src/connectors/. To build a connector for a new data source, use the add-connector skill instead.
1. Identify the connector
Check src/connectors/ to see which connectors are available in this repo. Also check the canonical template at https://github.com/kombohq/company-brain/tree/main/src/connectors/ - a newer connector for the data source the user wants may already exist there and can be pulled in before building anything from scratch.
2. Find the required credentials
Read .env.example for the connector's env vars. Each var has a comment pointing to where credentials are created and what permissions are needed.
Copy .env.example to .env. Ask the user for the credential values.
3. Add GitHub Actions secrets
The same values that go in .env need to be added as repository secrets so CI can use them.
Find the exact secret names in .github/workflows/sync-<source>.yml - look for ${{ secrets.* }} references.
Direct the user to: https://github.com/<owner>/<repo>/settings/secrets/actions
4. Configure the CI workflow
The workflow files under .github/workflows/ are templates that ship with placeholder values. Before enabling them, read the connector's doc at docs/connectors/<source>.md to understand what needs to be customized.
Replace placeholder values. Each workflow ships with example URLs, subdomains, repo names, or other source-specific values (e.g. kombo.dev, owner/example, kombo-api). Update these to point at the real source before committing.
Rename and describe the workflow. Update the name: field at the top to reflect what it actually syncs (e.g. Sync Public docs instead of Sync Web). This makes the Actions tab readable when multiple workflows are running.
Enable the schedule. Uncomment the schedule: block and set a cron expression that fits how often the source changes (times are UTC).
Stagger schedules across connectors. When multiple workflows run at the same time, the commit-and-push step serializes via rebase, adding latency and noise. Spread cron times.
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.
- 2mo ago First seen · 98 lines · 63 tokens per session scan A 81074db624d1
setup-connector is a skill published in the GitHub repository kombohq/company-brain (27 stars, last pushed 3mo ago), licensed MIT. It adds 63 tokens to every session and 1,424 once invoked, about $0.0003 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 skills, from other repositories
groq-inference
Ultra-fast LLM inference on custom LPU hardware. OpenAI-compatible API at api.groq.com. Lowest latency in the industry (500-1000+ tok/s). Supports chat completions, vision, audio (Whisper STT + TTS), tool calling, JSON mode, and streaming. Free tier available. Inference only — no training.
better-t-stack
Create or extend an end-to-end type-safe TypeScript project with Better-T-Stack (create-better-t-stack). Use when the user wants to start, scaffold or bootstrap an app, API, fullstack project or monorepo with any of Next.js, TanStack Router or Start, React Router, Nuxt, Svelte, Solid, Astro, React Native, Hono…
protocolsio-integration
Integration with protocols.io API for managing scientific protocols. This skill should be used when working with protocols.io to search, create, update, or publish protocols; manage protocol steps and materials; handle discussions and comments; organize workspaces; upload and manage files; or integrate protocols.io…
bunqueue
Use when building or operating bunqueue queues, workers, durable workflows, agent turns, MCP tools, retries, cron or dependency flows.
tauri-django-react
Agents should invoke this skill for Tauri + Django + React desktop apps, especially backend lifecycle, CORS/auth, frontend integration, mandatory light/dark theming, German/English i18n, build packaging, dual desktop/web deployment, Rust commands, and platform-specific gotchas.
bun
Use this skill when the user says 'bun', 'bun runtime', 'bun install', 'bun test', 'bun build', 'Bun.serve', 'bun:sqlite', 'Bun.file', 'Bun shell', 'bun --compile'. Builds TypeScript/JavaScript backends and tools on the Bun runtime: Bun.serve HTTP/WebSocket servers, bun:sqlite, file I/O, Bun Shell scripts, the…