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-deploy-awsnpx skills add flyteorg/flyte-agent-plugins --skill flyte-deploy-awsgit clone --depth 1 https://github.com/flyteorg/flyte-agent-pluginsWhat 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.00095 | $0.15821 |
| Opus 5 | $0.00048 | $0.07911 |
| Sonnet 5 | $0.00019 | $0.03164 |
| Haiku 4.5 | $0.00010 | $0.01582 |
Grade A, and why
flyte-deploy-aws scanned grade A with 1 finding 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 2d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -sL https://raw.githubusercontent.com/kubernetes-sigs/aws-load-balancer-controller/v3.4.0/docs/install/iam_policy.json -o alb-iam-policy.json How it starts
The opening of the file, as written. The whole thing — 940 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Deploying Flyte v2 on AWS (EKS + RDS + S3 + ALB)
Flyte v2 ships as a single unified binary (flyte-binary-v2) plus a separate console
image. One HTTP ingress serves the console (/v2), the flyteidl2.* Connect API, and
auth-discovery — there is no separate gRPC port. You scale it vertically.
The chart does NOT provision infrastructure. Stand up four things first:
EKS cluster, S3 bucket, PostgreSQL (RDS), and (for external access) an ingress
controller. This skill does all four with eksctl + aws + helm, then installs the
flyte-binary chart (the v2 chart; defaults to flyte-binary-v2 + flyteconsole-v2).
Get the chart first. Install from the published Helm repo — this is what the official
docs do, and the released chart pins the Flyte image tag to the chart version (see Image
selection in Step 5). Also helm pull --untar a local copy so the TaskAction CRD file is on
disk for the Step 5 idempotency check:
helm repo add flyteorg https://flyteorg.github.io/flyte && helm repo update
helm pull flyteorg/flyte-binary --untar # ./flyte-binary/templates/crds/flyte.org_taskactions.yaml now resolves
(Alternatively clone the repo — git clone https://github.com/flyteorg/flyte — and install
from the local ./charts/flyte-binary path for the bleeding-edge chart; its default image tag
is a floating :latest, so pair it with pullPolicy: Always — see Image selection.) Official
docs: https://www.union.ai/docs/v2/flyte/oss-deployment/aws-deployment/. Validated end-to-end
on EKS.
Replace every placeholder in angle brackets and the example hostnames/IDs with your own.
Prerequisites & decisions
- CLIs:
awsv2,eksctl≥ 0.227 (older caps out at k8s 1.29 — see gotcha),kubectl,helm,jq. - Admin (or EKS+RDS+IAM+S3+EC2) creds. STS/SSO works — export the 3 env vars + region.
- eksctl writes the kubeconfig context (e.g.
<user>@flyte-v2.<region>.eksctl.io). Passkubectl --context <ctx>(andhelm --kube-context <ctx>) per command rather thankubectl config use-context— that way you don't mutate the operator's current context. - Decide: region, name prefix, and exposure: ALB+TLS needs a Route53 zone + ACM cert;
ALB HTTP-only needs neither (reached at the auto
*.elb.amazonaws.comname) — the simplest default when you own no domain. (This skill provisions RDS PostgreSQL for the DB; an in-cluster Postgres is out of scope here — RDS is assumed by Steps 3–5.)
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.
- 2d ago First seen · 940 lines · 95 tokens per session scan A 8ef4365bf1de
flyte-deploy-aws is a skill published in the GitHub repository flyteorg/flyte-agent-plugins (2 stars, last pushed 5d ago), licensed Apache-2.0. It adds 95 tokens to every session and 15,821 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 1 finding (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
kagent-dev
Development guide for kagent's v1alpha3 Harness and AgentTemplate CRDs, AgentInstance gRPC control plane, upstream A2A integration, Substrate runtime provisioning, tests, generation, and PR workflow. Use for any implementation, debugging, review, or CI task in the kagent repository.
timoni
Use when deploying applications to Kubernetes with Timoni. Covers installing and upgrading module instances from OCI registries, composing multi-app deployments with bundles, injecting values from clusters or CI with runtimes, targeting multiple clusters, and authoring, testing, signing and publishing modules with CUE.
azmon-mirroredcatalogs-operations-cli
Brings Azure Monitor, Application Insights, and Log Analytics telemetry into Fabric as Eventhouse external delta tables and correlates it with business data. Use to onboard observability data, judge whether latency or availability affected revenue, or build a Real-Time dashboard and Operations Agent over it.
durable-objects
Create and review Cloudflare Durable Objects. Use when building stateful coordination (chat rooms, multiplayer games, booking systems), implementing RPC methods, SQLite storage, alarms, WebSockets, or reviewing DO code for best practices. Covers Workers integration, wrangler config, and testing with Vitest. Biases…
ship-web-games
Package, deploy, and verify a playable Three.js or web game. Use for release builds, asset delivery, private/public deployment, production smoke tests, browser proof, release notes, rollback readiness, and cleanup of temporary QA resources.
hyperpod-version-checker
Check and compare software component versions on SageMaker HyperPod cluster nodes - NVIDIA drivers, CUDA toolkit, cuDNN, NCCL, EFA, AWS OFI NCCL, GDRCopy, MPI, Neuron SDK (Trainium/Inferentia), Python, and PyTorch. Use when checking component versions, verifying CUDA/driver compatibility, detecting version mismatches…