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-cli-autonomy)<a href="https://agentmods.dev/rules/rkawaishi/workato-dev-kit/workato-cli-autonomy"><img src="https://agentmods.dev/badge/rules/rkawaishi/workato-dev-kit/workato-cli-autonomy/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-cli-autonomy"><img src="https://agentmods.dev/badge/rules/rkawaishi/workato-dev-kit/workato-cli-autonomy.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.01255 |
| Opus 5.5 | $0.00000 | $0.00502 |
| Sonnet 5.5 | $0.00000 | $0.00251 |
| Haiku 4.5 | $0.00000 | $0.00126 |
Grade A, and why
workato-cli-autonomy 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 — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Claude Code autonomy rule: do not ask the user for what the CLI/API can do
Principle
Before asking the user to "do X in the Workato UI", always check the steps below. Asking the user to do something the CLI or API can do for you is a waste of their time and undermines the value of automation.
The 4 checks to run before asking the user
Go through them in order. Stop at the first one that applies. Only ask the user if none does.
workato <command> --helpto see every option.- Example:
workato init --helpreveals--project-name, which can create a new project non-interactively.
- Example:
workato <command> <subcommand> --helpfor sub-options.- Example:
workato connections create --helpmay show--input '{"...": "..."}'for passing credentials as JSON.
- Example:
python3 scripts/workato-api.py --helpfor the API helper.- It complements the Platform CLI for API operations the CLI doesn't expose (jobs, recipes list as JSON, sdk push, etc.).
- Call the API through a custom connector.
- If steps 1–3 don't cover it, consider hitting the Workato Platform API directly via
__adhoc_http_action.
- If steps 1–3 don't cover it, consider hitting the Workato Platform API directly via
Operations that the CLI / API covers (don't ask the user)
| Goal | Command |
|---|---|
| Create a new project | workato init --project-name <name> --non-interactive --profile <profile> |
| Switch to an existing project | workato projects use "<name>" |
| List projects | workato projects list |
| Workspace info | workato workspace |
| Pull a project | workato pull |
| Push a project | workato push (--restart-recipes / --delete available) |
| List assets (DT, custom connectors, properties, etc.) | workato assets [--folder-id <id>] |
| List recipes | workato recipes list or python3 scripts/workato-api.py recipes list |
| Start / stop a recipe | workato recipes start --id <id> / workato recipes start --all |
| Swap a recipe's connection | workato recipes update-connection |
| Validate recipe JSON | workato recipes validate <file> |
| Create a connection (when auth params can be JSON-ified) | workato connections create --provider <p> --name <n> --input '<json>' |
| Create a shell connection (auth-less placeholder) | workato connections create --provider <p> --name <n> --shell-connection |
| List connections | workato connections list |
| Get connection pick-list | workato connections pick-list |
| Show required parameters for a connector | workato connectors parameters --provider <p> |
| Create a data table | workato data-tables create --name <n> --schema-json '<json>' |
| List data tables | workato data-tables list |
| Manipulate properties | workato properties list / workato properties upsert |
| List / show jobs | python3 scripts/workato-api.py jobs list/get |
| Look up pre-built connector info | python3 scripts/workato-api.py connectors list-platform |
| List custom connectors | python3 scripts/workato-api.py connectors list-custom |
| Push a custom connector (recommended) | python3 scripts/workato-api.py sdk push --connector <path> [--connector-id <id>] |
| Manage OAuth profiles | workato oauth-profiles ... |
| Manage API clients | workato api-clients ... |
| Create an API collection from OpenAPI | workato api-collections create |
| AI-friendly CLI doc search | workato guide search/topics/content |
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 · 95 lines · 1,255 tokens per session scan A 5cc8261a7729
workato-cli-autonomy 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 1,255 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).