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-sdk-shipnpx skills add flyteorg/flyte-agent-plugins --skill flyte-sdk-shipgit 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-sdk-ship)<a href="https://agentmods.dev/skills/flyteorg/flyte-agent-plugins/flyte-sdk-ship"><img src="https://agentmods.dev/badge/skills/flyteorg/flyte-agent-plugins/flyte-sdk-ship.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.00106 | $0.02522 |
| Opus 5 | $0.00053 | $0.01261 |
| Sonnet 5 | $0.00021 | $0.00504 |
| Haiku 4.5 | $0.00011 | $0.00252 |
Grade D, and why
flyte-sdk-ship scanned grade D with 3 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
| `Permission denied` on Docker socket | Add user to `docker` group: `sudo usermod -aG docker $USER` | Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
&& rm -rf /var/lib/apt/lists/* Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
"git", "curl", "wget", How it starts
The opening of the file, as written. The whole thing — 388 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Flyte 2 SDK Ship Skill
Generate images, Dockerfiles, and dependency configurations for Flyte 2 tasks.
Grounding References
| Resource | URL |
|---|---|
| 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/ |
| CLI API reference | https://www.union.ai/docs/v2/union/api-reference/flyte-cli/ |
| flyte-sdk source | https://github.com/flyteorg/flyte-sdk |
| Example code | https://github.com/unionai/unionai-examples |
| Flyte MCP tools | Available via the flyte-cluster and flyte-docs MCP servers |
Ground unfamiliar APIs in real examples. When unsure of a current Flyte 2 API, or for a pattern not shown below, and the flyte-docs search tools are available, search them first — by exact symbol (TaskEnvironment, flyte.io.File, map_task), since matching is literal substring, not semantic — then adapt a real example rather than inventing one, and cite the file or section you pulled it from. (Flyte 2 is not flytekit; priors are often wrong.)
flyte.Image — Programmatic Image Definition
Use flyte.Image to define task container images in Python. Flyte builds and pushes them automatically.
From Debian Base
import flyte
env = flyte.TaskEnvironment(
name="etl-pipeline",
image=flyte.Image.from_debian_base(python_version=(3, 12)).with_pip_packages(
"pandas", "polars", "pyarrow", "boto3",
).with_system_packages(
"git", "curl", "wget",
),
)
From Existing Image
env = flyte.TaskEnvironment(
name="ml-training",
image=flyte.Image.from_base(
"ghcr.io/flyteorg/flyte:py3.12-v2", # base image
).with_pip_packages(
"torch", "transformers", "datasets",
),
)
Image from uv Script Metadata
When using a # /// script header, Flyte can derive the image from the script's dependencies:
# /// script
# requires-python = ">=3.12"
# dependencies = [
# "pandas",
# "polars",
# ]
# ///
# Flyte reads the script metadata and builds the image automatically
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 · 388 lines · 106 tokens per session scan D b42f5c71947b
flyte-sdk-ship is a skill published in the GitHub repository flyteorg/flyte-agent-plugins (2 stars, last pushed 6d ago), licensed Apache-2.0. It adds 106 tokens to every session and 2,522 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it D with 3 findings (asks for root, recursive force delete, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
compute-env-setup
Set up a reproducible Feynman compute environment for research jobs. Use when a task needs Python/R packages, GPU libraries, containers, Modal, SSH, caches, or managed model runtime setup.
toolset-design
Design and validate new MCP toolsets, tools, and tool changes. Use when planning a new toolset, adding tools to an existing toolset, reviewing a toolset PR, or deciding whether a new tool is warranted. Covers the full lifecycle: eval-first validation, tool design methodology, consolidation patterns, and review…
nvca-chart-release
Release NVCA Operator chart changes from the native monorepo source to the vendored Helm chart. Use when updating the vendored NVCA Operator chart, changing NVCA image refs, publishing helm-nvca-operator, or validating the chart against a self-managed control plane.
nvca-values-customization
Customize NVCA Operator Helm chart values in the native monorepo. Use when modifying vendored defaults, changing stack-derived install values, adding deployment-time overrides, or updating scripts under deploy/helm/nvca-operator.
portainer-mcp-hygiene
How to drive the Portainer MCP server's tools correctly — both reading and mutating. Reading: project responses with select (JMESPath), where the heavy fields live (snapshots, status blocks, managed fields), how to handle non-JSON Docker/K8s proxy endpoints (container and pod logs, stats, exec), and how to interpret…
node-logs
Retrieve logs from a Kubernetes node — systemd units (journalctl) or files under /var/log. Use when you need node-level evidence: containerd, kubelet, kernel/OOM, or anything the pod's own log cannot show. Three access paths in order: hostscript (SSH), nodescript (debug pod), and localscript against the kubelet log…