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 onboardgit 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/onboard)<a href="https://agentmods.dev/skills/rkawaishi/workato-dev-kit/onboard"><img src="https://agentmods.dev/badge/skills/rkawaishi/workato-dev-kit/onboard.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.00046 | $0.02053 |
| Opus 5 | $0.00023 | $0.01026 |
| Sonnet 5 | $0.00009 | $0.00411 |
| Haiku 4.5 | $0.00005 | $0.00205 |
Grade A, and why
onboard 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 — 164 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/onboard
Bootstrap the organization knowledge base from Workato assets that already exist before the kit was adopted.
Most teams adopt this kit when their Workato workspace is already full of projects and custom connectors. /onboard pulls all of that down and runs the existing learn / sync / catalog skills over it, so docs/ and org/docs/ start out populated with the patterns, built-in actions, schemas and connector details this organization actually uses — making every later /create-recipe run sharper.
This skill is a thin orchestrator. It does not pull, learn, sync or catalog anything itself — it sequences the existing skills and never reimplements their logic.
Usage
/onboard— onboard every remote project and connector/onboard --projects "<a>","<b>"— limit to specific projects/onboard --resume— continue an interrupted run from the progress report/onboard --dry-run— show the plan and scope, execute nothing
Skills it orchestrates
| Step | Skill invoked | Writes to |
|---|---|---|
| Pull | /pull-project --all (or --projects) |
projects/ |
| Connectors | /sync-connectors --all |
docs/connectors/, connectors/docs/ |
| Learn recipes | /learn-recipe <project> (per project) |
org/docs/ |
| Patterns | /learn-pattern |
org/docs/patterns/recipe-patterns/ |
| Catalog | /catalog scan |
projects/CATALOG.md |
/onboard only invokes these — see each skill for its own behaviour.
Progress report
/onboard keeps a single artifact, org/onboarding-report.md, that doubles as the resume checkpoint and the final summary. It is a checklist of steps and per-project status. --resume reads it and skips everything already marked [x]; a fresh run creates it.
# Onboarding report
Started: <YYYY-MM-DD HH:MM> Last updated: <YYYY-MM-DD HH:MM>
Scope: all remote projects (or: projects a, b, c)
## Steps
- [x] Pull projects (12/12)
- [x] Sync connectors (8 pre-built, 2 custom)
- [ ] Learn recipes (7/12 projects)
- [ ] Learn patterns
- [ ] Catalog
## Per-project (learn-recipe)
- [x] Sales - Common
- [ ] [App] IT Onboarding ← resume here
...
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 · 164 lines · 46 tokens per session scan A a1cd888cde64
onboard is a skill published in the GitHub repository rkawaishi/workato-dev-kit (5 stars, last pushed 7d ago), licensed MIT. It adds 46 tokens to every session and 2,053 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…