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.
git clone --depth 1 https://github.com/rkawaishi/workato-dev-kitWrote 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/rules/rkawaishi/workato-dev-kit/workato-project-structure)<a href="https://agentmods.dev/rules/rkawaishi/workato-dev-kit/workato-project-structure"><img src="https://agentmods.dev/badge/rules/rkawaishi/workato-dev-kit/workato-project-structure/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/rules/rkawaishi/workato-dev-kit/workato-project-structure"><img src="https://agentmods.dev/badge/rules/rkawaishi/workato-dev-kit/workato-project-structure.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.00000 | $0.00835 |
| Opus 5.5 | $0.00000 | $0.00334 |
| Sonnet 5.5 | $0.00000 | $0.00167 |
| Haiku 4.5 | $0.00000 | $0.00084 |
Grade A, and why
workato-project-structure 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 — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Workato project directory structure
Recommended layout
Organize a project's assets into per-kind subfolders.
projects/<project-name>/
├── .workatoenv # project config (auto-generated)
├── <app-name>.lcap_app.json # Workflow App definition (root)
├── <app-name>.lcap_app.png # Workflow App icon (root)
├── Recipes/ # recipes
│ ├── <name>.recipe.json
│ └── fnc_<name>.recipe.json # Recipe Function
├── Pages/ # Workflow App pages
│ ├── <name>.lcap_page.json
│ └── <name>.lcap_page.zip
├── Connections/ # connections
│ └── <prefix>_<provider>.connection.json
├── Data Tables/ # Data Table schemas
│ └── <name>.workato_db_table.json
├── Insights/ # Insights queries
│ └── <name>.insights_query.json
├── Agents/ # Genie / MCP Server / Skills
│ ├── <name>.agentic_genie.json
│ ├── <name>.agentic_genie.png
│ ├── <name>.agentic_skill.json
│ └── <name>.mcp_server.json
Files that belong at the project root
Keep these at the project root:
.workatoenv— Platform CLI configuration*.lcap_app.json/*.lcap_app.png— Workflow App definition and icon
Mapping folder names to Workato
The local folder structure is reflected on Workato by workato push.
The zip_name and folder fields inside each JSON must include the folder path:
{
"zip_name": "Recipes/my_recipe.recipe.json",
"name": "My recipe",
"folder": "Recipes"
}
For files at the project root, leave folder: "".
Applying this to new projects
When /create-recipe, /create-workflow-app, or /create-genie generates new files, follow this layout and put each artifact in the right subfolder.
Reorganizing existing projects
Treat the result of workato pull as the source of truth. The safe path is to reorganize folders in the Workato UI first, then pull. If you move files locally instead, update every zip_name and folder reference.
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 · 98 lines · 0 tokens per session scan A 74872fe08b30
workato-project-structure is a cursor rule published in the GitHub repository rkawaishi/workato-dev-kit (5 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 835 tokens. 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 cursor rules, from other repositories
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
prefer-assertions-over-defensive-checks
Prefer assertions over defensive checks when data is guaranteed to be valid.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
config-validation-and-normalization
Config validation and normalization responsibilities (defineConfig normalizes, the orm section schema validates and resolves paths, the loader reports per-section diagnostics).