workato-project

A set of project rules for the Workato Dev Kit, a toolkit for building Workato automations. It explains the workspace layout for recipes, connections, apps, data tables, agents, connectors, and documentation.

In plain words
What is it for?
Guiding edits across Workato recipe projects, Workflow Apps, AI agents, custom connectors, documentation, and the organization’s separate knowledge layer.
Why use it?
It gives developers a shared map of where different Workato files belong and how organization-specific knowledge relates to the kit.

Cursor rule

Install

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.

agentmods
npx agentmods add rules/rkawaishi/workato-dev-kit/workato-project
Clone the repo
git clone --depth 1 https://github.com/rkawaishi/workato-dev-kit
Per session 1,923 This file is loaded in full into every session.
When invoked 1,923 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.01923 $0.01923
Opus 5 $0.00962 $0.00962
Sonnet 5 $0.00385 $0.00385
Haiku 4.5 $0.00192 $0.00192

Measured 2d ago against content hash 2567a387fa24, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

workato-project 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.

framework/cursor/rules/workato-project.mdc · 123 lines

How it starts

The opening of the file, as written. The whole thing — 123 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Workato Dev Kit

A toolkit for AI-editor-driven automation development on Workato (enterprise iPaaS). Covers recipe development, Workflow App construction, AI agents (Genie / MCP), and custom-connector development.

Repository structure (dual-repo)

This repository is the framework; it does not contain any organization-specific recipe projects.

  • projects/<project-name>/ — Workato recipe projects (managed via Platform CLI)
    • Recipes/ — recipes and Recipe Functions
    • Pages/ — Workflow App pages
    • Connections/ — connections
    • Data Tables/ — Data Table schemas
    • Agents/ — Genies / MCP servers / skills
    • Insights/ — Insights queries
  • connectors/ — custom connectors (Connector SDK)
  • docs/logic/ — recipe logic (if, loop, error handling, formulas, triggers, etc.)
  • docs/connectors/ — pre-built connector knowledge base (139+ entries)
  • docs/platform/ — platform features (Workflow Apps, MCP, Agent Studio, etc.)
  • docs/patterns/ — design patterns (shared assets, etc.)
  • docs/connector-sdk/ — Connector SDK reference
  • org/docs/ — organization knowledge layer. Overrides / corrections / org-specific info on top of docs/. The kit never touches it (see the org-knowledge-overlay rule).
kit/ (submodule) projects/ / connectors/
Contents skills, rules, docs recipes, pages, connectors
Nature framework (generic) organization-specific
Git management workato-dev-kit repository workspace repository

Knowledge lookup order

When you reference docs/<path>, always check the matching org/docs/<path> too (read both when present; the org version wins on conflicts). See the org-knowledge-overlay rule for details.

Recipe development

  1. docs/connectors/ (+ org/docs/connectors/) — triggers, actions, and fields for pre-built connectors
  2. connectors/docs/ — triggers, actions, and fields for custom connectors
  3. docs/logic/ (+ org/docs/logic/) — composing logic steps (including datapill notation)
  4. docs/platform/ (+ org/docs/platform/) — understanding platform features
  5. .cursor/rules/ — JSON format and project structure
  6. docs/patterns/recipe-patterns/ (+ org/docs/patterns/recipe-patterns/) — recipe construction patterns
  7. projects/docs/patterns/ — legacy patterns (read-only for backwards compatibility; record new patterns under org/docs/patterns/recipe-patterns/)
  8. docs/patterns/ (+ org/docs/patterns/) — deployment guide, shared-asset patterns

Read the full file on GitHub · 123 lines

Changes

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.

  1. 2d ago First seen · 123 lines · 1,923 tokens per session scan A 2567a387fa24

Subscribe to this mod's changes

workato-project is a cursor rule published in the GitHub repository rkawaishi/workato-dev-kit (5 stars, last pushed 2d ago), licensed MIT. It adds 1,923 tokens to every session, about $0.0096 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.