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-deploy-awsgit 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-deploy-aws)<a href="https://agentmods.dev/skills/flyteorg/flyte-agent-plugins/flyte-deploy-aws"><img src="https://agentmods.dev/badge/skills/flyteorg/flyte-agent-plugins/flyte-deploy-aws/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-deploy-aws"><img src="https://agentmods.dev/badge/skills/flyteorg/flyte-agent-plugins/flyte-deploy-aws.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.00095 | $0.15821 |
| Opus 5.5 | $0.00038 | $0.06328 |
| Sonnet 5.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 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.
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.
- 1mo 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 (3 stars, last pushed 14d ago), licensed Apache-2.0. It adds 95 tokens to every session and 15,821 once invoked, about $0.0004 per session on Opus 5.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
gke-compute-classes
Configures, optimizes, and troubleshoots GKE ComputeClasses. Use when configuring Spot VMs with on-demand fallback, targeting specific accelerators (GPUs/TPUs) or machine families, restricting ComputeClass access, or debugging pending pods related to node pool auto-creation. Do not use for cluster-level Node Auto…
gke-reliability
Improves GKE workload reliability, using PDBs, health probes, and topology spread constraints. Use when configuring GKE workload reliability, setting up PDBs, or configuring GKE health probes (liveness, readiness, startup). Don't use for generating K8s YAML manifests (use gke-manifest-generation) or disaster recovery…
gke-workload-security
Audits, configures, and hardens workload-level security controls for Google Kubernetes Engine (GKE) applications and namespaces. Covers running security audits (auditcluster.sh), enforcing Network Policies (default-deny and Dataplane V2 logging), isolating high-risk pods inside GKE Sandbox (gVisor), enforcing Pod…
cloud-architect
Designs cloud architectures, creates migration plans, generates cost optimization recommendations, and produces disaster recovery strategies across AWS, Azure, and GCP. Use when designing cloud architectures, planning migrations, or optimizing multi-cloud deployments. Invoke for Well-Architected Framework, cost…
nemo-automodel-launcher-config
Configure NeMo AutoModel job launches for interactive runs, Slurm clusters, and SkyPilot cloud execution.
azure-mgmt-botservice-dotnet
Azure Resource Manager SDK for Bot Service in .NET. Management plane operations for creating and managing Azure Bot resources, channels (Teams, DirectLine, Slack), and connection settings. Triggers: "Bot Service", "BotResource", "Azure Bot", "DirectLine channel", "Teams channel", "bot management .NET", "create bot".