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.
/plugin marketplace add rkawaishi/workato-dev-kitnpx agentmods add plugins/rkawaishi/workato-dev-kit/claudegit clone --depth 1 https://github.com/rkawaishi/workato-dev-kitGrade A, and why
workato-dev-kit 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 2d 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.
What it actually says
{
"name": "workato-dev-kit",
"description": "Build Workato recipes, Workflow Apps, Genies and custom connectors with an AI coding agent. Adds the knowledge layer and the asset types the Workato Labs toolchain does not cover.",
"version": "0.1.0",
"author": {
"name": "rkawaishi",
"url": "https://github.com/rkawaishi/workato-dev-kit"
},
"homepage": "https://github.com/rkawaishi/workato-dev-kit",
"license": "MIT",
"keywords": [
"workato",
"ipaas",
"integration",
"recipe",
"workflow-app",
"genie",
"mcp",
"connector-sdk"
],
"agents": [
"./agents/workato-builder.md"
],
"hooks": {
"PreToolUse": [
{
"matcher": "Bash",
"hooks": [
{
"type": "command",
"command": "${CLAUDE_PLUGIN_ROOT}/hooks/validate-before-push.sh"
}
]
},
{
"matcher": "Bash|Read|Edit|Write|NotebookEdit|Grep|Glob",
"hooks": [
{
"type": "command",
"command": "${CLAUDE_PLUGIN_ROOT}/hooks/block-credential-read.sh"
}
]
}
],
"PostToolUse": [
{
"matcher": "Bash",
"hooks": [
{
"type": "command",
"command": "${CLAUDE_PLUGIN_ROOT}/hooks/sync-docs-after-sdk-push.sh"
}
]
}
]
}
}
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.
- 2d ago First seen · 58 lines scan A d2eac2ba7eb3
workato-dev-kit is a plugin published in the GitHub repository rkawaishi/workato-dev-kit (5 stars, last pushed 2d ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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 plugins, from other repositories
atlassian-mcp-server
Connect to Atlassian products including Jira and Confluence. Search and create issues, access documentation, manage sprints, and integrate your development workflow with Atlassian's collaboration tools.
scrumboy-board-operator
Agent plugin with Skills for operating Scrumboy boards through its MCP and Agoragentic APIs.
enablement-crm-pack
CRM workflow bundle with reusable context, account planning, deal inspection, forecasting, and renewals.
beans-prime
Configure Claude Code to track work using Beans.
rook-maintainer
Maintainer-grade skills for rook (github.com/rook/): code review, backlog triage, systemic-PR campaigns, and the rook house conventions they enforce.
obw
Obsidian Workspace — project-scoped vault productivity (capture / notes / PM). Skills-only: owns folder layout and templates; runs the Obsidian CLI directly via the official obsidian-cli skill.