flyte-migrate-control-flow

flyte-migrate-control-flow is a skill for Claude Code, Codex from flyteorg/flyte-agent-plugins. It costs 89 tokens per session (3,108 once invoked), scanned A, original, Apache-2.0.

A migration guide for replacing Flyte 1 workflow-control features with ordinary Python in Flyte 2. Flyte is a system for defining and running data and machine-learning workflows; the guide covers branching, parallel work, dynamic workflows, and failure handling.

In plain words
What is it for?
Use it when converting conditionals, dynamic fan-out, map tasks, failure handlers, or other parallel workflow logic to Flyte 2.
Why use it?
Flyte 1 and Flyte 2 express these workflow behaviors differently, so direct translations can be confusing or incorrect.

Skill for Claude CodeCodex

Part of the flyte plugin — 21 skills, 2 MCP servers shipped together

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.

agentmods
npx agentmods add skills/flyteorg/flyte-agent-plugins/flyte-migrate-control-flow
Any agent
npx skills add flyteorg/flyte-agent-plugins --skill flyte-migrate-control-flow
Clone the repo
git clone --depth 1 https://github.com/flyteorg/flyte-agent-plugins

Made for: Claude Code, Codex.

Or install flyte, the plugin that ships this one along with the rest of its 21 skills, 2 MCP servers.

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.

agentmods badge for flyte-migrate-control-flow

README.md
[![agentmods](https://agentmods.dev/badge/skills/flyteorg/flyte-agent-plugins/flyte-migrate-control-flow.svg)](https://agentmods.dev/skills/flyteorg/flyte-agent-plugins/flyte-migrate-control-flow)
Your own site
<a href="https://agentmods.dev/skills/flyteorg/flyte-agent-plugins/flyte-migrate-control-flow"><img src="https://agentmods.dev/badge/skills/flyteorg/flyte-agent-plugins/flyte-migrate-control-flow.svg" alt="Measured on agentmods" height="20"></a>
Per session 89 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,108 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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.

ModelPer sessionOnce invoked
Fable 5 $0.00089 $0.03108
Opus 5 $0.00044 $0.01554
Sonnet 5 $0.00018 $0.00622
Haiku 4.5 $0.00009 $0.00311

Measured 3d ago against content hash 81a22e3287e7, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

flyte-migrate-control-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 3d 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.

plugins/flyte/skills/flyte-migrate-control-flow/SKILL.md · 357 lines

How it starts

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

Flyte 1 to 2 Migration: Control Flow and Parallelism

Flyte 1 expressed branching, dynamic fan-out, and failure handling through DSL constructs (conditional(), @dynamic, @workflow(on_failure=...)) and map_task. In Flyte 2 these are all ordinary Python, because orchestration runs as real Python at runtime. Native if/elif/else replaces the conditional DSL, plain task loops replace @dynamic, try/except replaces on_failure, and flyte.map / asyncio.gather replace map_task.

Grounding References

Resource URL
Migration guide (Control flow) https://www.union.ai/docs/v2/flyte/user-guide/migration/flyte-2/control-flow/
Migration guide (Parallelism) https://www.union.ai/docs/v2/flyte/user-guide/migration/flyte-2/parallelism/
Official docs https://www.union.ai/docs/v2/flyte
Docs index (LLMs) https://www.union.ai/docs/v2/flyte/llms.txt
SDK API reference https://www.union.ai/docs/v2/union/api-reference/flyte-sdk/
Example code https://github.com/unionai/unionai-examples
Flyte MCP tools Available via flyte-mcp server

Conditional Execution

The conditional() DSL becomes ordinary Python if / elif / else — for example, choosing a model based on dataset size.

Flyte 1

from flytekit import task, workflow, conditional

@task
def train_gradient_boosting(n_rows: int) -> str:
    return f"trained gradient boosting on {n_rows} rows"

@task
def train_logistic_regression(n_rows: int) -> str:
    return f"trained logistic regression on {n_rows} rows"

@workflow
def main(n_rows: int) -> str:
    # Pick the model based on dataset size.
    return (
        conditional("model_choice")
        .if_(n_rows > 10_000)
        .then(train_gradient_boosting(n_rows=n_rows))
        .else_()
        .then(train_logistic_regression(n_rows=n_rows))
    )

Flyte 2

import flyte

env = flyte.TaskEnvironment(name="conditional")

@env.task
def train_gradient_boosting(n_rows: int) -> str:
    return f"trained gradient boosting on {n_rows} rows"

@env.task
def train_logistic_regression(n_rows: int) -> str:
    return f"trained logistic regression on {n_rows} rows"

# Branching is now ordinary Python control flow -- no conditional() DSL.
@env.task
def main(n_rows: int) -> str:
    if n_rows > 10_000:
        return train_gradient_boosting(n_rows)
    return train_logistic_regression(n_rows)

Read the full file on GitHub · 357 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.

  1. 3d ago First seen · 357 lines · 89 tokens per session scan A 81a22e3287e7

Subscribe to this mod's changes

flyte-migrate-control-flow is a skill published in the GitHub repository flyteorg/flyte-agent-plugins (2 stars, last pushed 2d ago), licensed Apache-2.0. It adds 89 tokens to every session and 3,108 once invoked, about $0.0004 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.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

obra/superpowers · 37 tokens

auto-perf-optimize

Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.

microsoft/vscode · 62 tokens

chat-perf

Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.

microsoft/vscode · 51 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens