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 rkawaishi/workato-dev-kit --skill learn-patterngit 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/learn-pattern)<a href="https://agentmods.dev/skills/rkawaishi/workato-dev-kit/learn-pattern"><img src="https://agentmods.dev/badge/skills/rkawaishi/workato-dev-kit/learn-pattern/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/skills/rkawaishi/workato-dev-kit/learn-pattern"><img src="https://agentmods.dev/badge/skills/rkawaishi/workato-dev-kit/learn-pattern.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.00038 | $0.01298 |
| Opus 5.5 | $0.00015 | $0.00519 |
| Sonnet 5.5 | $0.00008 | $0.00260 |
| Haiku 4.5 | $0.00004 | $0.00130 |
Grade A, and why
learn-pattern 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 — 163 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/learn-pattern
A Workato expert records construction patterns into org/docs/patterns/recipe-patterns/.
The goal is to document know-how the expert already has. A reference recipe can be supplied as optional source material.
The write target is a single location in the org knowledge layer (the kit submodule's docs/ is left alone). See @.claude/rules/org-knowledge-overlay.md.
Usage
/learn-pattern— start recording a pattern (interactive)/learn-pattern "Pagination loop"— specify the pattern name/learn-pattern "Approval workflow" "additional caveats"— append to an existing pattern/learn-pattern <file-path>— supply a recipe as reference material (the pattern itself is decided interactively)
Procedure
1. Confirm the expert's intent
First survey existing patterns (read kit canonical and org sides; org wins on conflicts):
docs/patterns/recipe-patterns/_index.md— kit canonical, generic patterns.org/docs/patterns/recipe-patterns/_index.md— org-recorded patterns (if present).projects/docs/patterns/_index.md— legacy org-domain patterns (if present; read-only for backwards compatibility).
Ask the user what they want to record:
What are we recording?
A. A new pattern (e.g. pagination loop, batch processing, etc.)
B. An addition to an existing pattern (caveats, variations, etc.)
Existing patterns:
- org/docs/patterns/recipe-patterns/: <list pattern names>
- (legacy) projects/docs/patterns/: <list pattern names if any>
Skip this question and proceed when the argument already makes the name / intent clear.
2. Interview the pattern
Ask the expert for the key points. You don't need to ask everything — build the structure from what they say:
- When is it used — what kind of requirement makes you reach for this composition?
- Composition highlights — which steps go where?
- Why this composition — why pick this over alternatives?
- Gotchas — pitfalls you only learn the hard way.
If a reference recipe is supplied, read the .recipe.json and summarize its structure for the expert. Use it to make the pattern concrete by cross-referencing the expert's description.
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 · 163 lines · 38 tokens per session scan A f7b9371de001
learn-pattern is a skill published in the GitHub repository rkawaishi/workato-dev-kit (5 stars, last pushed 1mo ago), licensed MIT. It adds 38 tokens to every session and 1,298 once invoked, about $0.0002 per session on Opus 5.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
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Optimize the meaningful UI available immediately from a Next.js route on an initial load (hard navigation) or named client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route and entry point at a time; the shipped test then guards…