Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/rkawaishi/workato-dev-kitnpx agentmods add skills/rkawaishi/workato-dev-kit/pull-projectWrote 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/pull-project)<a href="https://agentmods.dev/skills/rkawaishi/workato-dev-kit/pull-project"><img src="https://agentmods.dev/badge/skills/rkawaishi/workato-dev-kit/pull-project/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/pull-project"><img src="https://agentmods.dev/badge/skills/rkawaishi/workato-dev-kit/pull-project.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.00025 | $0.00774 |
| Opus 5.5 | $0.00010 | $0.00310 |
| Sonnet 5.5 | $0.00005 | $0.00155 |
| Haiku 4.5 | $0.00003 | $0.00077 |
Grade A, and why
pull-project 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 — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/pull-project
Pull a project from the remote via the Workato Platform CLI.
Usage
/pull-project— pull the current project/pull-project <project-name>— switch to the specified project and pull/pull-project --all— pull every remote project/pull-project --projects "<a>","<b>"— pull a specific subset of remote projects/pull-project --list— show the list of remote projects
Procedure
0. Pre-pull check (mandatory)
Pull silently overwrites uncommitted local changes. Check the workspace repository for uncommitted changes in the target project:
git status projects/<project-name>/
If there are uncommitted changes, suggest the user commits or stashes them before pulling. Pulling without asking can lose in-progress edits. For --all, repeat this check per project. If the workspace repository is not under git, skip this check.
0.5. Ensure .workatoignore (mandatory, before every pull)
workato pull silently overwrites and deletes local files. Before pulling a project, make sure its .workatoignore exists so local-only artifacts (the catalog files, custom connector source, …) survive. Run the kit helper once the project directory exists — for a brand-new project, after workato init:
bash scripts/ensure-workatoignore.sh "projects/<project-name>"
The helper creates .workatoignore from the base template (templates/workatoignore.template) when absent, or appends only the missing entries otherwise. It is idempotent and never removes or reorders existing lines.
The template ignores *.custom_adapter.{rb,json} by default: a connector pulled into the project would otherwise be re-pushed by a later workato push and could roll the connector back to an older version. If this project intentionally manages a connector as code, tell the user to delete those two lines from .workatoignore (keeping the >>> opt-out <<< marker comments) — the helper will then leave the opt-out alone.
No argument / project name supplied
# When a name is supplied, switch first
workato projects use "<project-name>"
Then run Step 0.5 for the project, and pull:
workato pull
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 · 70 lines · 25 tokens per session scan A 256dffff7230
pull-project is a skill published in the GitHub repository rkawaishi/workato-dev-kit (5 stars, last pushed 1mo ago), licensed MIT. It adds 25 tokens to every session and 774 once invoked, about $0.0001 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
story-readiness
Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
handle-linkedin-connection-request-signal
Use this skill when someone sends a team member an inbound LinkedIn connection request. An inbound request is a deliberate, ACTIVE first-party intent signal — meaningfully stronger than a passive profile view — and it deserves different scoring rules. The skill resolves and enriches the requester, gates them through…
remove
Remove a deployed framework or addon from the current workspace.