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.
npx agentmods add skills/flyteorg/flyte-agent-plugins/flyte-migrate-tasks-workflowsnpx skills add flyteorg/flyte-agent-plugins --skill flyte-migrate-tasks-workflowsgit clone --depth 1 https://github.com/flyteorg/flyte-agent-pluginsWrote 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/flyteorg/flyte-agent-plugins/flyte-migrate-tasks-workflows)<a href="https://agentmods.dev/skills/flyteorg/flyte-agent-plugins/flyte-migrate-tasks-workflows"><img src="https://agentmods.dev/badge/skills/flyteorg/flyte-agent-plugins/flyte-migrate-tasks-workflows.svg" alt="Measured on agentmods" 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 | $0.00103 | $0.02325 |
| Opus 5 | $0.00051 | $0.01162 |
| Sonnet 5 | $0.00021 | $0.00465 |
| Haiku 4.5 | $0.00010 | $0.00232 |
Grade A, and why
flyte-migrate-tasks-workflows 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.
How it starts
The opening of the file, as written. The whole thing — 259 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Flyte 1 to 2 Migration: Tasks and Workflows
The biggest structural change in Flyte 2 is that everything is a task. The Flyte 1 @task, @workflow, and @dynamic decorators all collapse into a single @env.task on a flyte.TaskEnvironment, and a "workflow" is now just a task that calls other tasks. This skill covers the structural shift, sequential ordering without the >> operator, nested subworkflows, TaskEnvironment configuration basics, and the full @task parameter mapping.
Grounding References
| Resource | URL |
|---|---|
| Migration guide | https://www.union.ai/docs/v2/flyte/user-guide/migration/flyte-2/tasks-and-workflows/ |
| 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 |
The Structural Shift
In Flyte 1 you decorated units of work with @task, composed them with @workflow, and used @dynamic for runtime-generated graphs. In Flyte 2 you create one flyte.TaskEnvironment that carries the configuration, then decorate every function — leaf tasks and orchestrating "workflows" alike — with @env.task. There is no separate @workflow decorator: the entrypoint is just a task that calls other tasks.
Hello World: Tasks and Workflows
A @task plus @workflow becomes two @env.tasks, where the entrypoint task calls the others. Sequential calls are naturally ordered — no >> operator required.
Flyte 1
import flytekit
@flytekit.task
def say_hello(name: str) -> str:
return f"Hello, {name}!"
@flytekit.task
def to_upper(greeting: str) -> str:
return greeting.upper()
@flytekit.workflow
def main(name: str) -> str:
greeting = say_hello(name=name)
return to_upper(greeting=greeting)
Flyte 2
import flyte
env = flyte.TaskEnvironment(name="hello_world")
@env.task
def say_hello(name: str) -> str:
return f"Hello, {name}!"
@env.task
def to_upper(greeting: str) -> str:
return greeting.upper()
# The "workflow" is now just a task that calls other tasks.
@env.task
def main(name: str) -> str:
greeting = say_hello(name)
return to_upper(greeting)
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.
- 3d ago First seen · 259 lines · 103 tokens per session scan A bd2e2281b0c5
flyte-migrate-tasks-workflows is a skill published in the GitHub repository flyteorg/flyte-agent-plugins (2 stars, last pushed 6d ago), licensed Apache-2.0. It adds 103 tokens to every session and 2,325 once invoked, about $0.0005 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.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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.
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.
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.
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.
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…