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 agentmods add skills/rkawaishi/workato-dev-kit/auto-learnnpx skills add rkawaishi/workato-dev-kit --skill auto-learngit 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/skills/rkawaishi/workato-dev-kit/auto-learn)<a href="https://agentmods.dev/skills/rkawaishi/workato-dev-kit/auto-learn"><img src="https://agentmods.dev/badge/skills/rkawaishi/workato-dev-kit/auto-learn.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 | $0.00074 | $0.05347 |
| Opus 5 | $0.00037 | $0.02674 |
| Sonnet 5 | $0.00015 | $0.01069 |
| Haiku 4.5 | $0.00007 | $0.00535 |
Grade A, and why
auto-learn 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 5d 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 — 395 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/auto-learn
Drive the Workato UI through Claude in Chrome and actively collect input / output fields for every operation (trigger / action) of the target connector, then append the results to docs/connectors/<provider>.md.
Prerequisites
- Editor: Claude Code only (Cursor / Codex CLI / Gemini CLI cannot run this — they have no Chrome MCP).
- Extension: Claude in Chrome must be installed and connected. Without a connection, calls like
tabs_context_mcpornavigatewill fail (check connection state withmcp__Claude_in_Chrome__list_connected_browsers). - Workato login: a tab signed in to the target workspace UI must exist (the skill does not log in for you).
Design principles (important)
This skill is designed for autonomy first, breadth second. The goal is to spread some level of field coverage across many connectors, not to nail every type or nesting structure perfectly. Fine-grained corrections come later from manual recipes or /learn-recipe.
- No interaction: a single invocation tries every op of the target connector. Do not ask the user mid-run. With no basis for a decision, defaults → skip + log.
- Fail-soft: wrap each op in try / catch and keep going on failure. One op's failure does not abort the run.
- Record-driven: append what you got, mark what you didn't as "learning failure / partial learning". Report at the end.
- UI only: no new fetch / XHR against internal APIs (reverse engineering is strictly forbidden). Only passive observation of responses triggered by UI actions is allowed. See
@docs/patterns/auto-learn-ui-operations.md.
Usage
/auto-learn <provider>
Options:
--recipe-id <id>— recipe ID used for verification (default: inferred from the conventional recipe name or from the previous tab's URL).--workspace-url <url>— workspace base URL (default: previous tab).--force— relearn even if field details already exist in docs.--triggers-only/--actions-only— narrow the scope.--sandbox <json>— test data for dynamic schemas (see below).--followups— no-UI mode. Aggregate the## Learning summarysections of existingdocs/connectors/*.mdand print to stdout. A<provider>argument restricts to one connector; otherwise aggregates across all 7+ connectors. The execution flow (Phases 1–5) does not run. See "Followups mode" at the end of this file.
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.
- 5d ago First seen · 395 lines · 74 tokens per session scan A 90b2d22c824c
auto-learn is a skill published in the GitHub repository rkawaishi/workato-dev-kit (5 stars, last pushed 5d ago), licensed MIT. It adds 74 tokens to every session and 5,347 once invoked, about $0.0004 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
v8-jit
V8 JIT optimization patterns for writing high-performance JavaScript in Next.js server internals. Use when writing or reviewing hot-path code in app-render, stream-utils, routing, caching, or any per-request code path. Covers hidden classes / shapes, monomorphic call sites, inline caches, megamorphic deopt, closure…
use-agent-browser-for-airi
Test AIRI display-model imports with agent-browser across stage-tamagotchi Electron, stage-web, and stage-pocket mobile web layouts. Use when uploading and verifying contributor-supplied Live2D ZIP, VRM, or MMD ZIP/PMX/PMD files through AIRI's model selector, including onboarding bypass, format-specific import…
opencli-sitemap-author
Use when creating or maintaining OpenCLI site sitemaps: agent-facing navigation, page-state, action, workflow, API-reference, pitfall, and fallback knowledge for a website. Use after browser exploration discovers durable site context, when a sitemap is stale, or when promoting local site knowledge into the repo.
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
webapp-testing
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
interactive-login
How to complete browser/interactive logins (aws / gh / glab / gcloud). The platform backgrounds the login poller so it survives the human's browser round-trip — and when that does NOT work.