Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/rkawaishi/workato-dev-kitnpx agentmods add skills/rkawaishi/workato-dev-kit/sync-connectorsWrote 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/rkawaishi/workato-dev-kit/sync-connectors)<a href="https://agentmods.dev/skills/rkawaishi/workato-dev-kit/sync-connectors"><img src="https://agentmods.dev/badge/skills/rkawaishi/workato-dev-kit/sync-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.00049 | $0.02187 |
| Opus 5 | $0.00024 | $0.01094 |
| Sonnet 5 | $0.00010 | $0.00437 |
| Haiku 4.5 | $0.00005 | $0.00219 |
Grade A, and why
sync-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 — 259 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/sync-connectors
Collect connector metadata and update the documentation.
- Pre-built connectors: fetched from the Workato API → updates
docs/connectors/. - Custom connectors: parsed from
connector.rb→ updatesconnectors/docs/.
Usage
/sync-connectors <provider-name>— fetch and update info for one pre-built connector/sync-connectors <name1> <name2> ...— batch-update several pre-built connectors/sync-connectors --all— update every pre-built + custom connector/sync-connectors --check— diff existing docs against the API/sync-connectors --custom— scan and update every custom connector underconnectors//sync-connectors --custom <name>— scan and update only the specified custom connector
Data sources
Pre-built connectors
Primary source: the Workato API (via CLI)
# Triggers / actions for a specific connector (JSON)
python3 scripts/workato-api.py connectors list-platform --provider <name>
# List of custom connectors
python3 scripts/workato-api.py connectors list-custom
What the API gives you:
- Connector name (
name), display title (title). - Category, OAuth support, deprecated flag.
- Trigger list:
name,title,deprecated,bulk,batch. - Action list:
name,title,deprecated,bulk,batch.
What the API does not give you:
- Input / output field definitions (only available after the connection is configured).
- Field types and required/optional flags.
Custom connectors
Source: connector.rb (local parse)
Read the Ruby DSL in connectors/<name>/connector.rb directly. No API call. Claude reads the DSL and extracts:
title:— connector display name.actions:block — action names (hash keys),title,batch/bulkflags.triggers:block — trigger names (hash keys),title, and trigger type:poll+dedup→ Pollingwebhook_subscribe→ Webhook
object_definitions:— shared field definitions (the array inside thefieldslambda).input_fields/output_fields— field definitions:- For
object_definitions['name']references, resolve to the corresponding definition. - For inline arrays, extract directly.
- From each field, take
name,type,label,optional,hint.
- For
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 · 259 lines · 49 tokens per session scan A 07396fc76991
sync-connectors is a skill published in the GitHub repository rkawaishi/workato-dev-kit (5 stars, last pushed 6d ago), licensed MIT. It adds 49 tokens to every session and 2,187 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-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…