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 trayio/tray-plugins --skill research-connectorgit clone --depth 1 https://github.com/trayio/tray-pluginsWrote 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/trayio/tray-plugins/research-connector)<a href="https://agentmods.dev/skills/trayio/tray-plugins/research-connector"><img src="https://agentmods.dev/badge/skills/trayio/tray-plugins/research-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/trayio/tray-plugins/research-connector"><img src="https://agentmods.dev/badge/skills/trayio/tray-plugins/research-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.00047 | $0.01553 |
| Opus 5.5 | $0.00019 | $0.00621 |
| Sonnet 5.5 | $0.00009 | $0.00311 |
| Haiku 4.5 | $0.00005 | $0.00155 |
Grade A, and why
research-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.
How it starts
The opening of the file, as written. The whole thing — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Research Connector
This skill is the fallback path for direct connector research from the parent agent — useful for trivial lookups (single small operation, no DDL fields, no polymorphism) or for ad-hoc exploration. For real workflow builds, prefer delegating to the Researcher subagent (see build-workflow#step-2-research-connectors); the subagent absorbs verbose schemas and returns a step-level prescriptive result, keeping the parent's context lean.
If you do follow this process directly, the schemas you see from list_connector_operations are compacted by default — advanced fields stripped, polymorphic branches replaced with _collapsed markers carrying expand: ['<propName>'] hints. Echo a hint verbatim into the next call's expand array when you actually need a collapsed branch; otherwise leave it collapsed. Pass include_advanced: true only when an advanced field is genuinely required, and include_output_schema: false for terminal steps where nothing downstream consumes the result.
Follow this process exactly. Do NOT skip steps or guess field values.
Stop Conditions
Immediately stop and ask the user if:
- DDL operations don't reveal field values/options
- Field names contain ambiguous terms (status, active, priority, etc.)
- Custom fields are referenced (__c suffix fields)
- Authentication fails or is missing
- Sample queries return errors
Step 1: Discover Connector
Call list_connectors with the connector name. Record exact name, version, and service details. When multiple versions exist, use the latest.
Step 2: Check Authentication
Use the connector's service name (from Step 1's connector.service.name — e.g. google-sheets, slack, salesforce) to filter authentications. Always prefer service_name over keyword search — auth display names are user-supplied (e.g. an auth named "Sheets" backs service.name === "google-sheets") and keyword search by name routinely misses the right auth.
list_authentications(service_name: "<connector.service.name>")
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 · 97 lines · 47 tokens per session scan A 6adc12e7f2da
research-connector is a skill published in the GitHub repository trayio/tray-plugins (10 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 47 tokens to every session and 1,553 once invoked, about $0.0002 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-31.
Other skills, from other repositories
mem0-oss-to-platform
Plan, then execute, a migration of a project from the mem0 open-source / self-hosted SDK (local Memory class) to the mem0 Platform / hosted SDK (MemoryClient). TRIGGER when: the developer wants to move, switch, or migrate mem0 off OSS/self-hosted to the hosted API, e.g. "migrate my mem0 setup to the platform", "switch…
agui-dotnet-protobuf
Use the protobuf wire transport (instead of the default Server-Sent Events) for an AG-UI connection with the AG-UI .NET SDK — a compact binary event stream negotiated via the Accept header. USE FOR: making an AGUIChatClient prefer protobuf by wiring an AGUIEventStreamHandler with ProtobufEventStreamFormatter (then…
azure-mgmt-botservice-dotnet
Azure Resource Manager SDK for Bot Service in .NET. Management plane operations for creating and managing Azure Bot resources, channels (Teams, DirectLine, Slack), and connection settings. Triggers: "Bot Service", "BotResource", "Azure Bot", "DirectLine channel", "Teams channel", "bot management .NET", "create bot".
fastapi-router-py
Create FastAPI routers with CRUD operations, authentication dependencies, and proper response models. Use when building REST API endpoints, creating new routes, implementing CRUD operations, or adding authenticated endpoints in FastAPI applications.
migrate-segw-to-rap
Reverse-engineer a SEGW-built OData V2 service (MPC/DPC/MPCEXT/DPCEXT) into a modern RAP V4 service — tables, CDS views (interface + projection), behavior definitions, draft entities, service definition + binding. Use when asked to "migrate this SEGW service to RAP", "convert OData V2 to V4 RAP", "modernize this…
api-design
Use when settling the contract of an API you expose, before implementation: resources/URLs, REST vs GraphQL, versioning, one RFC 9457 error envelope, pagination, idempotency — emitted as OpenAPI 3.1. NOT implementing the endpoints (that is fastapi/nestjs/go/nodejs), NOT auth hardening (that is secure-coding), NOT…