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 skills add flyteorg/flyte-agent-plugins --skill flyte-migrategit 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)<a href="https://agentmods.dev/skills/flyteorg/flyte-agent-plugins/flyte-migrate"><img src="https://agentmods.dev/badge/skills/flyteorg/flyte-agent-plugins/flyte-migrate/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/flyteorg/flyte-agent-plugins/flyte-migrate"><img src="https://agentmods.dev/badge/skills/flyteorg/flyte-agent-plugins/flyte-migrate.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.00114 | $0.04831 |
| Opus 5.5 | $0.00046 | $0.01932 |
| Sonnet 5.5 | $0.00023 | $0.00966 |
| Haiku 4.5 | $0.00011 | $0.00483 |
Grade A, and why
flyte-migrate 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 — 355 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Flyte 1 to 2 Migration Skill
This is the entry point for migrating a Flyte 1 (flytekit) codebase to Flyte 2 (flyte). Flyte 2 is a fundamental shift: there is no @workflow decorator, everything is a @env.task, orchestration runs as real Python at runtime, and parallelism is expressed with asyncio. This skill explains the overall shift, gives a recommended migration strategy, covers hybrid v1/v2 pipelines during the transition, and routes to the sibling skills that handle each theme in depth.
Grounding References
| Resource | URL |
|---|---|
| Migration guide | https://www.union.ai/docs/v2/flyte/user-guide/migration/flyte-2/ |
| 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 overall v1 to v2 shift
Two conceptual shifts motivate almost every change — pure Python execution and the asynchronous model — after which most migrations come down to a couple of mechanical moves.
flytekit(package) becomesflyte. Imports change fromimport flytekittoimport flyte.pyflyte(CLI) becomesflyte. The command-line tool was renamed.- Everything is a task. In Flyte 1,
@workflowfunctions were constrained to a DSL subset of Python that compiled to a static DAG. In Flyte 2 there is no@workflowdecorator: everything is a@env.task, and a "workflow" is simply a task that calls other tasks. Loops, conditionals, andtry/exceptwork anywhere. - Async is the parallelism model. Flyte 2 is built on
asyncio, with the Flyte orchestrator acting as the event loop, scheduling awaited tasks across distributed infrastructure.awaitsignals where a task can be scheduled in parallel, andasyncio.gathertells the orchestrator that a set of tasks are independent.
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 · 355 lines · 114 tokens per session scan A e65402a27d72
flyte-migrate is a skill published in the GitHub repository flyteorg/flyte-agent-plugins (3 stars, last pushed 14d ago), licensed Apache-2.0. It adds 114 tokens to every session and 4,831 once invoked, about $0.0005 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
agent-platform-model-registry
Agent Platform Model Registry Management. Use when you need to upload, list, describe, update, or delete machine learning models (and their versions) in the Agent Platform Model Registry. Don't use for model training, model deployment to endpoints, or managing non-Agent Platform models.
foundry-config-setup
Resolve missing setup caused by a hardcoded Foundry project endpoint or model in a sample. Use when a sample fails because it uses a placeholder/hardcoded projectendpoint (for example "https://your-project.services.ai.azure.com") or a hardcoded model instead of reading them from the environment.
google-cloud-solution-agentic-analytics-spark-knowledge-catalog
Discovers requirements and designs an end-to-end governed agentic analytics solution using Knowledge Catalog and Managed Service for Apache Spark (Lightning Engine). Use when designing data science and analytics workflows across structured and unstructured distributed data (including in S3, Azure Blob, AlloyDB, and…
training-check
Interactively monitor training metrics from the current Codex session, periodically checking WandB or fallback logs for NaN, divergence, plateaus, and broken runs.
nemo-automodel-launcher-config
Configure NeMo AutoModel job launches for interactive runs, Slurm clusters, and SkyPilot cloud execution.
finetuning
Fine-tune models on Microsoft Foundry using SFT (supervised), DPO (preference), or RFT (reinforcement with graders). Covers dataset preparation, training job submission, deployment, and evaluation. USE FOR: fine-tune, SFT, DPO, RFT, training data, grader, distillation, fine-tuned model, training job, large file…