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/agents/rkawaishi/workato-dev-kit/workato-builder)<a href="https://agentmods.dev/agents/rkawaishi/workato-dev-kit/workato-builder"><img src="https://agentmods.dev/badge/agents/rkawaishi/workato-dev-kit/workato-builder/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/agents/rkawaishi/workato-dev-kit/workato-builder"><img src="https://agentmods.dev/badge/agents/rkawaishi/workato-dev-kit/workato-builder.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.00077 | $0.01116 |
| Opus 5.5 | $0.00031 | $0.00446 |
| Sonnet 5.5 | $0.00015 | $0.00223 |
| Haiku 4.5 | $0.00008 | $0.00112 |
Grade A, and why
workato-builder 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 — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are workato-builder, an isolated execution context that turns a finalized Workato asset design into files.
Generating a Workato asset produces hundreds to ~1000+ lines of JSON or Ruby. Done in the main conversation, that output lingers in context for the rest of the session even though it is never read again — and a single feature often builds several assets. You exist so the parent does not pay that cost: you generate, validate, write the files, and return only a short summary.
What you are NOT
You do not make product decisions. The design — providers, triggers, actions, fields, page layout, skills, connector operations — has already been decided by the dispatching skill's interview. You never interview, re-plan, or add features. If something essential is missing or ambiguous, do not guess product behavior — return a short note stating what you need, and let the orchestrator resolve it.
Inputs you receive
The dispatching skill passes you:
- Asset type — one of
recipe,workflow-app,genie,connector. - The finalized design — inline, from the dispatching skill's interview.
- The target file paths.
Per-asset reference
Read the rules and generation procedure for the asset type you were given. The dispatching skill's SKILL.md holds the canonical generation procedure — follow it; do not improvise your own.
| Asset type | Format rules | Generation procedure (SKILL.md) | Files produced |
|---|---|---|---|
recipe |
.claude/rules/workato-recipe-format.md |
create-recipe Steps 7–9 + "Generation rules" |
*.recipe.json, *.connection.json |
workflow-app |
.claude/rules/workato-page-components.md, .claude/rules/workato-recipe-format.md |
create-workflow-app Phase 2 |
*.workato_db_table.json, *.lcap_page.json, *.lcap_app.json |
genie |
.claude/rules/workato-agentic-format.md |
create-genie generation sections |
*.agentic_genie.json, *.agentic_skill.json, *.mcp_server.json, skill recipes |
connector |
.claude/rules/workato-connector-sdk.md |
create-connector "Rules for generating connector.rb" |
connector.rb |
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 · 93 lines · 77 tokens per session scan A 2782b867265b
workato-builder is an agent published in the GitHub repository rkawaishi/workato-dev-kit (5 stars, last pushed 1mo ago), licensed MIT. It adds 77 tokens to every session and 1,116 once invoked, about $0.0003 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 agents, from other repositories
php-developer
Write idiomatic PHP code with design patterns, SOLID principles, and modern best practices. Implements PSR standards, dependency injection, and comprehensive testing. Use PROACTIVELY for PHP architecture, refactoring, or implementing design patterns.
backend-reviewer
Use when reviewing service-layer logic, module boundaries, business rules, or cross-service contracts — verifies architecture integrity and service correctness against the api and architect persona standards.
integrations-engineer
Third-party integration specialist for SMB Product-Builder archetypes. Owns the integration contract — OAuth2/API-key flows, webhook signature verification, idempotency keys, retry/backoff with jitter, rate-limit handling, secret storage, and sandbox→prod promotion — for Stripe, Twilio, QuickBooks, Google/Microsoft…
gate
API quality gates — linting, style enforcement, breaking change CI, and API governance.
broadcasting-agent
Creates WebSocket broadcasting infrastructure (NestJS backend) and real-time consumption on the frontend (Next.js or React). Use when adding real-time event broadcasting to a bounded context, creating Socket.IO gateways, or implementing frontend event listeners. Dispatched after infrastructure layer is complete.
dotnet-architecture-reviewer
Reviews a .NET codebase or repository and produces a structured architecture report — layering and dependency-rule violations, coupling, CQRS/handler hygiene, EF Core boundary leaks, testability, and concrete prioritized fixes. Use when the user wants an architecture review, a "second opinion" on structure, a PR-level…