A guide for creating or editing a Keboola flow, which runs data configurations in a chosen order. A flow can also run on a schedule.

Use it to chain existing Keboola configurations, change their order, edit an existing flow, or add a schedule.

It helps turn separate extractors, transformations, and writers into an ordered pipeline without changing the wrong project. It makes the intended sequence and optional schedule explicit.

build-flow — Skill for Claude Code and Codex by keboola/mcp-server

Install

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.

Any agent

npx skills add keboola/mcp-server --skill build-flow

Clone the repo

git clone --depth 1 https://github.com/keboola/mcp-server

Made for: Claude Code, Codex.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/keboola/mcp-server/build-flow/github.svg)](https://agentmods.dev/skills/keboola/mcp-server/build-flow)

Your own site

<a href="https://agentmods.dev/skills/keboola/mcp-server/build-flow"><img src="https://agentmods.dev/badge/skills/keboola/mcp-server/build-flow/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/keboola/mcp-server/build-flow"><img src="https://agentmods.dev/badge/skills/keboola/mcp-server/build-flow.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 43 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,031 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00043	$0.01031
Opus 5.5	$0.00017	$0.00412
Sonnet 5.5	$0.00009	$0.00206
Haiku 4.5	$0.00004	$0.00103

Measured today against content hash ad5ee737a3ca, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

build-flow 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 today.

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.

integrations/chatgpt-plugin/skills/build-flow/SKILL.md · 62 lines

How it starts

The opening of the file, as written. The whole thing — 62 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Build a flow

Create a flow from existing configurations, or change an existing flow, in the one project the user confirms.

Input

Which configurations to run, in what order, and whether the flow needs a schedule. For an existing flow, its name or ID.

Steps

Pick the project. Call get_accessible_projects (with with_llm_instruction=true on the first call in the conversation) and ask the user which project the flow belongs in. Never pick a project on your own: confirm it. Do this even when the session looks scoped already or a data tool would work without it: this plugin always narrows the session to the projects the user confirms. If get_accessible_projects fails because no programmatic token is present, the login is bound to one project: confirm it with the user and skip step 2.
Scope the session to that project. Call set_project_scope with project_ids=[<the confirmed id>]. This must happen before any write. If the result carries a non-null scope_token, pass it on every later tool call. Every write below also passes the confirmed id as project_id: other conversations on the same login share the scope, and a scope they moved makes the write fail instead of landing in another project.
Get context. Call get_project_info with project_id=<the confirmed id>. It says whether conditional flows are enabled in the project, and its toolset_restrictions say whether the user's role may set schedules. If they say only read-only tools are available, tell the user they cannot create flows in this project and stop.
Collect the tasks. Find every configuration the flow should run with search (item_types=["configuration", "transformation"]) and confirm the list with the user. Each task needs a component ID and a configuration ID; use get_configs with configs=[...] when a search hit does not show them. Do not create the configurations here; a missing SQL transformation is built with the build-sql-transformation skill first.
Load the schema. Call get_flow_schema with flow_type="keboola.flow" when conditional flows are enabled, otherwise flow_type="keboola.orchestrator". Call get_flow_examples with the same type if you have not seen one in this conversation.
Show the plan. List the phases, the tasks in each phase and their order. Tasks in one phase run in parallel; phases run in order. Wait for the user to agree.
Create or update.
- New flow: call create_conditional_flow with project_id=<the confirmed id> for keboola.flow, or create_flow with project_id=<the confirmed id> for keboola.orchestrator. Give every phase and task an id and a name.
- Existing flow: find it with search and item_types=["flow"], read it with get_flows and flow_ids=[...], then call modify_flow with project_id=<the confirmed id>, its configuration_id=..., the flow_type=... it already has, a change_description=... and only the fields that change.
Schedule, if asked. Call modify_flow with project_id=<the confirmed id> and schedules=[...] for the schedule the user asked for. Confirm the cron expression and time zone with the user first. If toolset_restrictions from step 3 say the role cannot set schedules, tell the user and skip this step.
Run, if asked. Ask before running. Call run_job with project_id=<the confirmed id>, the flow's component_id=... and configuration_id=..., then follow it with get_jobs. On failure, continue with the debug-failed-job skill.
Report. Give the flow name, its phases, the schedule and the links the tools returned.

Read the full file on GitHub · 62 lines

Changes

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.

today First seen · 62 lines · 43 tokens per session scan A ad5ee737a3ca

Subscribe to this mod's changes

build-flow is a skill published in the GitHub repository keboola/mcp-server (85 stars, last pushed today), licensed MIT. It adds 43 tokens to every session and 1,031 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-10-23.

Project management data-platform etl-pipeline keboola-platform mcp mcp-server model-context-protocol

report-issue

File a bug or feature request against this repository (cyanheads/git-mcp-server) using the gh CLI. Use for tool logic bugs, git provider misbehavior, transport issues, auth/config problems, or new feature proposals.

cyanheads/git-mcp-server · 51 tokens

reviewing-sla-definitions

Reviewing ServiceNow SLA, OLA and underpinning-contract definitions and how they perform: breach rates per definition, overlapping or duplicated definitions on the same table and target, and definitions that never attach. Use when the user asks about SLA breaches by definition, too many SLAs, duplicate or conflicting…

jschuller/mcp-server-servicenow · 79 tokens

quick-capture

Use this skill to drop a new task into GSD Task Manager from any AI assistant that has the gsd-mcp-server connected.

vscarpenter/gsd-task-manager · 0 tokens

papi-plan

Invoke when starting a new PAPI cycle. Covers plan generation, board management, and cycle scoping rules.

getpapi/papi · 26 tokens

papi-idea

Invoke when submitting backlog ideas, registering docs, or filing research. Covers idea pipeline and doc registry conventions.