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 skills/trayio/tray-plugins/tray-connectorsnpx skills add trayio/tray-plugins --skill tray-connectorsgit 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/tray-connectors)<a href="https://agentmods.dev/skills/trayio/tray-plugins/tray-connectors"><img src="https://agentmods.dev/badge/skills/trayio/tray-plugins/tray-connectors.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.00072 | $0.04049 |
| Opus 5 | $0.00036 | $0.02024 |
| Sonnet 5 | $0.00014 | $0.00810 |
| Haiku 4.5 | $0.00007 | $0.00405 |
Grade A, and why
tray-connectors 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 6d 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 — 257 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Tray Core Connectors Reference
Consult this when building workflow steps with standard connectors.
For connectors not listed here, use research-connector to discover them via MCP tools.
Quick Version Table
Always verify versions with list_connectors — versions may vary by workspace.
| Connector | Name | Version | Use Case |
|---|---|---|---|
| Manual Trigger | noop |
1.1 |
Start manually |
| Scheduled Trigger | scheduled |
3.5 |
Time-based triggers |
| Callable Trigger | callable-trigger |
2.0 |
Called by other workflows |
| Boolean Condition | boolean-condition |
2.3 |
Two-way branch |
| Loop | loop |
1.3 |
Iterate arrays/objects |
| Break Loop | break-loop |
1.1 |
Exit/skip iterations |
| Delay | delay |
1.0 |
Pause execution |
| HTTP Client | http-client |
5.6 |
REST/HTTP APIs |
| Script (JS) | script |
3.3 / 3.4 |
Custom JavaScript |
| Python | python-script |
2.0 |
Python transformations |
| Call Workflow | call-workflow |
2.0 |
Invoke other workflows |
| Callable Response | callable-workflow-response |
1.0 |
Return data to caller |
| Send Email | send-email |
4.1 |
Email notifications |
| Terminate | terminate |
1.1 |
Stop execution |
For detailed examples of each connector, see core-connectors.md.
Triggers
Every workflow starts with exactly one trigger step, always named "trigger".
Picking the trigger from the user's prompt
The user's wording maps to a specific trigger connector. Pick deliberately — webhook is the wrong default for form/submit/manual prompts, but it's the right answer for "Stripe sends events to us" / "incoming HTTP from system X".
| User says… | Use |
|---|---|
| "form", "submit a form", "form fields", "form submission", "fill in" | form-trigger |
| "manual", "press a button", "run on-demand", "trigger it myself", "kick it off" | noop (operation trigger) |
| "scheduled", "every day at", "weekly", "cron", "at 9am" | scheduled |
| "called by another workflow", "callable", "invoked from", "shared workflow" | callable-trigger |
| "agent tool", "the agent calls", "tool the agent uses" | agent-tool-trigger |
| "API endpoint", "expose an API", "request/response API" | api-operation-trigger |
| "Slack message arrives", "new Slack event" | slack-trigger |
| "external system POSTs to us", "incoming webhook from ", " sends an HTTP payload" | webhook |
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 6d ago First seen · 257 lines · 72 tokens per session scan A 2b47059f20cc
tray-connectors is a skill published in the GitHub repository trayio/tray-plugins (9 stars, last pushed 18d ago), licensed Apache-2.0. It adds 72 tokens to every session and 4,049 once invoked, about $0.0004 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…