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 deploy-flyte-core-kindgit 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/deploy-flyte-core-kind)<a href="https://agentmods.dev/skills/flyteorg/flyte-agent-plugins/deploy-flyte-core-kind"><img src="https://agentmods.dev/badge/skills/flyteorg/flyte-agent-plugins/deploy-flyte-core-kind/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/deploy-flyte-core-kind"><img src="https://agentmods.dev/badge/skills/flyteorg/flyte-agent-plugins/deploy-flyte-core-kind.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.00155 | $0.07527 |
| Opus 5.5 | $0.00062 | $0.03011 |
| Sonnet 5.5 | $0.00031 | $0.01505 |
| Haiku 4.5 | $0.00015 | $0.00753 |
Grade A, and why
deploy-flyte-core-kind 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.
SDK's HTTP/2 calls fail while plain `curl` still looks fine. How it starts
The opening of the file, as written. The whole thing — 701 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Deploy flyte-core to a kind cluster with a local image
Stand up the split Flyte v2 deployment on kind:
eight Deployments from the flyte-core chart, a throwaway in-cluster PostgreSQL
and MinIO, and an image built from the user's own checkout. For evaluation and
chart development only — no TLS, no auth, static credentials, emptyDir
storage that dies with the pod.
Pick this skill over its siblings when:
| Situation | Skill |
|---|---|
Test the flyte-core chart, or a local build of the binary, on your laptop |
this skill |
| Single-binary Flyte on kind with hosted PostgreSQL + S3/R2 | deploy-flyte-kind |
Split flyte-core on real infrastructure (EKS + S3 + RDS) |
flyte-deploy-aws-core |
[!IMPORTANT] Why the image must be local Every component runs the same binary with a different
--componentflag (args: [--component, runs, ...]). That flag lives inmanager/cmd/on the commit that introduced the chart. The chart's default image (cr.flyte.org/flyteorg/flyte-binary-v2:latest) is built frommain, so until that commit merges the published image rejects the flag and all seven components CrashLoopBackOff. Build the image from the same checkout as the chart — this is not an optimization, it is the only way the chart runs today.
Step 0: Prerequisites and the checkout
Need on PATH: docker, kind, kubectl, helm. Confirm each before starting.
The chart and the image both come from one Flyte checkout. Confirm
charts/flyte-core/ exists in it:
ls charts/flyte-core/Chart.yaml
If it does not, the checkout predates the chart — check out the branch that
carries it (as of writing, flyte-core on github.com/Sovietaced/flyte; on
flyteorg/flyte master once merged). Ask the user which checkout to use;
never guess a path or clone over an existing one.
Check for an existing cluster before creating one:
kind get clusters
If a flyte cluster already exists, ask whether to reuse or recreate it. Reuse
is fine — but a cluster made with a plain kind create cluster has no host-port
mappings, and those cannot be added after creation (Step 1).
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 · 701 lines · 155 tokens per session scan A d1e87e02d3bb
deploy-flyte-core-kind is a skill published in the GitHub repository flyteorg/flyte-agent-plugins (3 stars, last pushed 14d ago), licensed Apache-2.0. It adds 155 tokens to every session and 7,527 once invoked, about $0.0006 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.
Other skills, from other repositories
deploy-docker-compose
Run the Omnigent server as a Docker compose stack (server + Postgres) on any Docker host — your laptop, a VPS, EC2 by hand, or as the base layer of any container-platform deploy. Invoke when the user wants to build the image, bring up the compose stack, debug the stack on a host they already have, or extend the stack…
bdd-container-update
Update the BDD test container image when its dependencies or runtime change. Determines version bump (major vs minor vs patch), rebuilds the Docker image, pushes to GitLab registry, and updates the image tag in starttest.sh. Test source (tests/, features/, scripts/, data/, conftest.py) is bind-mounted from the host…
securing-kubernetes-on-cloud
This skill covers hardening managed Kubernetes clusters on EKS, AKS, and GKE by implementing Pod Security Standards, network policies, workload identity, RBAC scoping, image admission controls, and runtime security monitoring. It addresses cloud-specific security features including IRSA for EKS, Workload Identity for…
detecting-privilege-escalation-in-kubernetes-pods
Detect and prevent privilege escalation in Kubernetes pods by monitoring security contexts, capabilities, and syscall patterns with Falco and OPA policies.
docker-socket-mount
Docker / containerd socket mounted into a container → host RCE. Common in CI runners, GitOps controllers (ArgoCD, Flux), and 'Docker-in-Docker' setups. Single-command escape via docker run --rm --privileged -v /:/host alpine chroot /host.
managing-astro-local-env
Manage local Airflow environment with Astro CLI (Docker and standalone modes). Use when the user wants to start, stop, or restart Airflow, view logs, query the Airflow API, troubleshoot, or fix environment issues. For project setup, see setting-up-astro-project.