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 skills add workato-devs/recipe-skills --skill datatable-recipesgit clone --depth 1 https://github.com/workato-devs/recipe-skillsWrote 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/workato-devs/recipe-skills/datatable-recipes)<a href="https://agentmods.dev/skills/workato-devs/recipe-skills/datatable-recipes"><img src="https://agentmods.dev/badge/skills/workato-devs/recipe-skills/datatable-recipes.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.00043 | $0.08168 |
| Opus 5 | $0.00022 | $0.04084 |
| Sonnet 5 | $0.00009 | $0.01634 |
| Haiku 4.5 | $0.00004 | $0.00817 |
Grade A, and why
datatable-recipes 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 7d 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 — 880 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Data Tables Recipes Skill - Agent Instructions
DEPENDENCY: Load the
workato-recipesbase skill first if not already loaded. This skill requires the base Workato knowledge for triggers, control flow, datapills, formulas, and recipe structure.
This skill provides Data Tables-specific knowledge for generating Workato recipes. It extends the workato-recipes base skill and focuses on the workato_db_table connector — Workato's internal relational data store.
CRITICAL: Pre-Generation Checklist
For EXISTING projects:
- Read existing data table
.recipe.jsonfiles to discover column UUIDs and table references - Read the
.workato_db_table.jsonfile if present in the project — it defines the table schema
For GREENFIELD projects:
- Ask the user for the table name and column names/types
- Column UUIDs are not portable — you cannot invent them. Either:
- Build the recipe in the Workato UI first, export, and use the UUIDs from the export
- Use placeholder UUIDs (e.g.,
COLUMN_UUID_email,COLUMN_UUID_status) and note they must be replaced after the table exists on the server
ALWAYS:
- Use descriptive
asaliases — e.g.,new_pending_approval,update_row_status - Include
dynamicPickListSelectionon the trigger and every action —{"table_id": "TableDisplayName"} - Remember: column names are UUIDs — not human-readable names. See UUID Column Mapping.
- Config uses
account_id: null— this is an internal connector with no external connection
Table of Contents
What ships with it
6 files 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.
- 7d ago First seen · 880 lines · 43 tokens per session scan A acb5d3bb7262
datatable-recipes is a skill published in the GitHub repository workato-devs/recipe-skills (18 stars, last pushed 8d ago), licensed MIT. It adds 43 tokens to every session and 8,168 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-30.
Other skills, from other repositories
event-store-design
Design and implement event stores for event-sourced systems. Use when building event sourcing infrastructure, choosing event store technologies, or implementing event persistence patterns.
convex-explain-app
Explain an existing Convex app — data model + relationships, public vs internal functions, auth/ownership model, components, a request→data flow — read from the schema and function surface. Read-only.
platform-custom-field-generate
Use this skill when users need to create, generate, or validate Salesforce Custom Field metadata. Trigger when users mention custom fields, field types, Roll-up Summary fields, Master-Detail relationships, Lookup relationships, formula fields, picklists, dependent (controlling) picklists, referencing a value set from…
openloomi-api
OpenLoomi ships a local-first HTTP API served from the desktop app (port 3414, fallback 3515). All auth, Memory, AI, RAG, Loop, and Audit data live in a local SQLite database — your data stays on your machine and the OpenLoomi app is the source of truth. The only externally-routed auth path is the Composio OAuth…
nornicdb-grpc
Drive NornicDB over gRPC — the Qdrant-compatible surface (Collections, Points, Snapshots) plus the additive NornicSearch service. Use when ingesting via Qdrant SDKs, migrating from Qdrant, or running hybrid text+vector search from a non-Bolt client. Covers connection, RPC catalog, collection→database mapping…
field-service-sobject-create-configure
Headless 360 REST API deployment step for creating sObject records. Handles describe-based field discovery, required-field derivation, entity-relationship ordering, and composite graph transactions. Use this skill when a designer skill (or a user directly) needs to create sObject records after design confirmation…