flyte-deploy-aws-core

flyte-deploy-aws-core is a skill for Claude Code from flyteorg/flyte-agent-plugins. It costs 130 tokens per session (7,054 once invoked), scanned A, original, Apache-2.0.

A guide for deploying Flyte v2, a workflow platform, on AWS using EKS, S3, RDS, and an application load balancer. It runs core services as separate deployments so each can be scaled independently.

In plain words
What is it for?
It is for operating the split Flyte core chart on AWS infrastructure and scaling services such as runs, actions, events, cache, and executor separately.
Why use it?
It provides a deployment pattern that separates failures and scaling for Flyte services instead of placing them all in one process.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the flyte plugin — 23 skills, 2 MCP servers shipped together

Good fit It is for operating the split Flyte core chart on AWS infrastructure and scaling services such as runs, actions, events, cache, and executor separately.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/flyteorg/flyte-agent-plugins/flyte-deploy-aws-core
Install

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.

Any agent
npx skills add flyteorg/flyte-agent-plugins --skill flyte-deploy-aws-core
Clone the repo
git clone --depth 1 https://github.com/flyteorg/flyte-agent-plugins

Made for: Claude Code.

Or install flyte, the plugin that ships this one along with the rest of its 23 skills, 2 MCP servers.

Wrote 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.

agentmods badge for flyte-deploy-aws-core

README.md
[![agentmods](https://agentmods.dev/badge/skills/flyteorg/flyte-agent-plugins/flyte-deploy-aws-core/github.svg)](https://agentmods.dev/skills/flyteorg/flyte-agent-plugins/flyte-deploy-aws-core)
Your own site
<a href="https://agentmods.dev/skills/flyteorg/flyte-agent-plugins/flyte-deploy-aws-core"><img src="https://agentmods.dev/badge/skills/flyteorg/flyte-agent-plugins/flyte-deploy-aws-core/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.

agentmods 80×15 button for flyte-deploy-aws-core

Your own site · 80×15
<a href="https://agentmods.dev/skills/flyteorg/flyte-agent-plugins/flyte-deploy-aws-core"><img src="https://agentmods.dev/badge/skills/flyteorg/flyte-agent-plugins/flyte-deploy-aws-core.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 130 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 7,054 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00130 $0.07054
Opus 5.5 $0.00052 $0.02822
Sonnet 5.5 $0.00026 $0.01411
Haiku 4.5 $0.00013 $0.00705

Measured 1mo ago against content hash b16b868ea7f9, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

flyte-deploy-aws-core 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 -s -X POST "http://$ALB/flyteidl2.project.ProjectService/ListProjects" \
plugins/flyte/skills/flyte-deploy-aws-core/SKILL.md · 505 lines

How it starts

The opening of the file, as written. The whole thing — 505 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Deploying Flyte v2 on AWS with the split flyte-core chart

flyte-core runs Flyte v2 as eight independent Deployments plus the console, instead of the single unified pod that flyte-binary ships. Same image (flyte-binary-v2), same flyteidl2.* Connect API — the binary just takes a --component <name> flag and starts only that service.

flyte-binary                       flyte-core
┌───────────────────┐              ┌──────┐┌───────┐┌──────┐┌─────┐
│ runs actions      │              │ runs ││actions││events││cache│
│ events cache      │   ────►      └──────┘└───────┘└──────┘└─────┘
│ dataproxy secret  │              ┌─────────┐┌──────┐┌────────┐┌───┐
│ executor app      │              │dataproxy││secret││executor││app│
└───────────────────┘              └─────────┘└──────┘└────────┘└───┘
   scale vertically                   scale each one independently

Which chart should you use?

flyte-binary (skill: flyte-deploy-aws) flyte-core (this skill)
Pods 1 + console 8 + console
Scaling vertical only per-component replicaCount
Blast radius one crash takes everything executor crash doesn't drop the API
Chart source published Helm repo (flyte-binary) published Helm repo (flyte-core, v2.x — see Step 5)
Config keys flyte-core-components.* configuration.*
Operational cost lowest more pods, more nodes, more moving parts

Default to flyte-binary unless the user has a concrete reason to split. Good reasons: they need >1 replica of a specific service, they want the executor isolated from the API, or they are testing the split topology itself. "It looks more production-grade" is not one — flyte-binary is the supported path today and flyte-core is at chart version 0.1.0.

⚠️ flyte-core is new and unreleased. It is not on flyteorg.github.io/flyte, its chart version is 0.1.0, and it carries the open issues in Known chart issues below. Tell the user this before starting. If they want the supported path, switch to flyte-deploy-aws.

Read the full file on GitHub · 505 lines

Files

What ships with it

1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

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.

  1. 1mo ago First seen · 505 lines · 130 tokens per session scan A b16b868ea7f9

Subscribe to this mod's changes

flyte-deploy-aws-core is a skill published in the GitHub repository flyteorg/flyte-agent-plugins (3 stars, last pushed 14d ago), licensed Apache-2.0. It adds 130 tokens to every session and 7,054 once invoked, about $0.0005 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-09-16.

Related

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…

google/skills · 83 tokens

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…

google/skills · 85 tokens

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…

google/skills · 171 tokens

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…

Jeffallan/claude-skills · 71 tokens

nemo-automodel-launcher-config

Configure NeMo AutoModel job launches for interactive runs, Slurm clusters, and SkyPilot cloud execution.

NVIDIA/skills · 30 tokens

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".

microsoft/skills · 78 tokens