OpenConnector is an open-source gateway that lets AI agents connect to accounts and actions from more than 1,000 software providers through a shared catalog. It is used by agents and applications through an SDK, CLI, MCP, HTTP, or OpenAPI, with credential handling and runtime controls for local, self-hosted, or hosted deployments.
Borrowing it
Nothing to install: this file belongs to oomol-lab/open-connector. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/oomol-lab/open-connector/main/.codex/skills/add-provider/SKILL.mdgit clone --depth 1 https://github.com/oomol-lab/open-connectorWrote 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/oomol-lab/open-connector/add-provider)<a href="https://agentmods.dev/skills/oomol-lab/open-connector/add-provider"><img src="https://agentmods.dev/badge/skills/oomol-lab/open-connector/add-provider/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/oomol-lab/open-connector/add-provider"><img src="https://agentmods.dev/badge/skills/oomol-lab/open-connector/add-provider.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00039 | $0.03621 |
| Opus 5 | $0.00019 | $0.01810 |
| Sonnet 5 | $0.00008 | $0.00724 |
| Haiku 4.5 | $0.00004 | $0.00362 |
Grade A, and why
add-provider 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 — 204 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Add Provider
Use this skill when adding or updating a provider in this repository. The goal is to produce provider code that looks native to this project, is locally runnable when execution is supported, and keeps the public catalog accurate for agents and users.
This is the agent-oriented workflow for CONTRIBUTING.md. Follow AGENTS.md for repository-wide style and verification rules.
Public Boundary
Keep the repository focused on open-source local execution:
- Do not describe non-public products, non-public migration sources, unreleased SDK behavior, deployment operations, or organization-specific workflows in provider code, docs, examples, or skill text.
- Do not expose compatibility fields, storage placeholders, or implementation details that have no clear public source and consumer.
- Do not paste OpenAPI or vendor tool output into the repository as provider action schemas. If the upstream surface is large, choose a small runnable subset and maintain schemas as source.
- A provider-local action-schema module such as
generated.tsis allowed only when it is hand-maintained as source and reviewed like the rest of the provider.src/providers/gorgias/generated.tsandsrc/providers/postman/generated.tspredate this rule and are grandfathered; a new module needs its own justification. - A new module must not carry vendor tool-description text verbatim: rewrite every action description in this project's voice. The action descriptions in
src/providers/postman/generated.tsare still Postman's own tool text, which is known debt rather than a precedent to copy. - Do not copy third-party logos, screenshots, API specs, documentation excerpts, generated schemas, or brand assets unless the project has the right to distribute them.
- Prefer official public URLs for
homepageUrl, API documentation references in comments when truly needed, and credential help text. - If you use a reference implementation, treat it only as behavioral evidence. Re-express the provider in this repository's architecture and remove non-public assumptions before finishing.
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 · +5 lines 76aee8f2f55e
- 7d ago Changed · +12 lines 7fad847d51c9
- 9d ago First seen · 187 lines · 39 tokens per session scan A a3c52998bac0
add-provider is a skill published in the GitHub repository oomol-lab/open-connector (5,657 stars, last pushed today), licensed Apache-2.0. It adds 39 tokens to every session and 3,621 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
vs-search-tuning-specify-policy-direction
Viking Search tuning for specified policy directions. Use this when the user provides specific queries, a type of query, or a business policy direction, and asks to boost, suppress, or fix a class of search results through request-parameter passthrough. You must only perform read-only baseline evaluation and…
vs-product-qa
Answer Viking AI Search product questions, CLI usage questions, API/auth questions, configuration questions, and troubleshooting questions by grounding every claim in either the installed vs CLI's own output or official Volcengine documentation. Never fabricate.
vs-search-tuning-partial-case
Use when the user provides 1-50 concrete bad-case search queries for one Viking Search app and wants local deterministic fixes. This skill only verifies request-level fine-operation interventions against a read-only baseline scene and delivers a console-ready configuration sheet, validated payloads, and a replay…
vs-user-onboarding
Guide a brand-new SearchCLI/vs user from first-time usage questions to sign-up, purchase of Viking AI Search, AK/SK setup, and a working authenticated CLI. Use when the user says they downloaded or installed SearchCLI/vs and asks how to use it, how to start, sign up, buy, or onboard.
vs-crawler
Crawl websites (news, blogs, papers, GitHub, product docs, RSS feeds) into a fixed-schema JSONL file, then create a dataset and a searchable application in Viking AI Search. Supports one-time crawl and scheduled recurring crawl with automatic incremental sync.
volcengine-documentation
Volcengine official documentation lookup helper. Supports both document search and full-content fetch across Volcengine products, developer tools, support content, best practices, pricing, deployment, troubleshooting, API, SDK, and policy pages.