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/deploy-flyte-kind-vmnpx skills add flyteorg/flyte-agent-plugins --skill deploy-flyte-kind-vmgit 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-kind-vm)<a href="https://agentmods.dev/skills/flyteorg/flyte-agent-plugins/deploy-flyte-kind-vm"><img src="https://agentmods.dev/badge/skills/flyteorg/flyte-agent-plugins/deploy-flyte-kind-vm.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.00137 | $0.04363 |
| Opus 5 | $0.00068 | $0.02181 |
| Sonnet 5 | $0.00027 | $0.00873 |
| Haiku 4.5 | $0.00014 | $0.00436 |
Grade F, and why
deploy-flyte-kind-vm scanned grade F with 4 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 4d 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.
curl -fsSL https://get.docker.com | sudo sh Reaches for credential fileshighPrivilege escalation
SSH keys, cloud credentials, git-credentials, .npmrc, /etc/shadow: reading these is how a config file becomes a credential leak.
doctl compute ssh-key import <name> --public-key-file ~/.ssh/id_ed25519.pub # prints the ID Downloads and executes remote codehighSupply chain
curl | sh runs whatever the server returns today, which is not necessarily what it returned when this was reviewed.
curl -fsSL https://get.docker.com | sh Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -fsSL https://get.docker.com | sh How it starts
The opening of the file, as written. The whole thing — 340 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Deploy Flyte on kind — local machine or a cloud VM
kind runs anywhere Docker runs, so the same Flyte-on-kind deploy works on your
own machine or on a cloud VM. This skill picks the host, provisions it if
it's a cloud VM, installs the prerequisites, and then runs the actual Flyte
deploy — the cluster, the hosted PostgreSQL + object store, the helm install, and
optional auth — by handing off to the deploy-flyte-kind skill. The only
things that change per host are where the commands run and how you reach the
API afterward.
For evaluation only. Single-node kind, static credentials, no workload identity. On a cloud VM the stack is reachable from the public internet, so the provisioning steps below restrict inbound 80/443 (and 22) to your own IP. For production, use the
flyte-deploy-awsskill instead.
This skill is guided: several steps need human-in-the-loop input — which host, confirming billable VM creation, SSH keys, and (in the deploy hand-off) the Supabase / R2 / S3 credentials. Ask; never invent account IDs, IPs, keys, or passwords.
Step 0: Choose the host
Ask the user where to run the cluster (use AskUserQuestion):
- Local machine — kind runs in your local Docker. Simplest; nothing to provision.
- DigitalOcean — a Droplet, provisioned with
doctl. - AWS EC2 — an instance, provisioned with the
awsCLI. - GCP Compute Engine — an instance, provisioned with
gcloud.
Then:
- Local machine → skip to Step 3 (nothing to provision). The whole deploy runs locally.
- A cloud VM → do Step 1 (provision) and Step 2 (define how remote commands run), then Step 3.
kind needs a few GB of headroom, so any VM should be at least 4 vCPU / 8 GB.
Step 1: Provision the cloud VM (skip for local)
First confirm the provider CLI is installed and authenticated locally, since these commands run on your machine:
# DigitalOcean
command -v doctl >/dev/null && doctl account get >/dev/null 2>&1 || echo "doctl: install and run 'doctl auth init'"
# AWS
command -v aws >/dev/null && aws sts get-caller-identity >/dev/null 2>&1 || echo "aws: install and configure credentials"
# GCP
command -v gcloud >/dev/null && gcloud auth list >/dev/null 2>&1 || echo "gcloud: install and run 'gcloud auth login'"
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.
- 4d ago First seen · 340 lines · 137 tokens per session scan F b2be74a1ac56
deploy-flyte-kind-vm is a skill published in the GitHub repository flyteorg/flyte-agent-plugins (2 stars, last pushed 2d ago), licensed Apache-2.0. It adds 137 tokens to every session and 4,363 once invoked, about $0.0007 per session on Opus 5. A static security scan graded it F with 4 findings (asks for root, reaches for credential files, downloads and executes remote code). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…