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 bex-co/bex --skill bex-deploygit clone --depth 1 https://github.com/bex-co/bexWrote 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/bex-co/bex/bex-deploy)<a href="https://agentmods.dev/skills/bex-co/bex/bex-deploy"><img src="https://agentmods.dev/badge/skills/bex-co/bex/bex-deploy/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/bex-co/bex/bex-deploy"><img src="https://agentmods.dev/badge/skills/bex-co/bex/bex-deploy.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.00052 | $0.03685 |
| Opus 5.5 | $0.00021 | $0.01474 |
| Sonnet 5.5 | $0.00010 | $0.00737 |
| Haiku 4.5 | $0.00005 | $0.00368 |
Grade A, and why
bex-deploy 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 yesterday.
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.
1. Retrieve the linked Markdown document directly with an available URL-fetching tool or HTTP client, such as `curl`. Do not substitute web-search summaries for the document. How it starts
The opening of the file, as written. The whole thing — 349 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Deploy to bex
bex supports Git-backed services and prebuilt Docker image services.
This skill covers Git-backed flows:
- Blueprint Method - Generate render.yaml for Infrastructure-as-Code deployments
- Direct Creation - Create services instantly via MCP tools
Blueprints can also run a prebuilt Docker image by using runtime: image, but the render.yaml still must live in a Git repo.
If there is no Git remote, stop and ask the user to either:
- Create/push a Git remote (can be minimal if only the Blueprint is needed), or
- Use the bex dashboard/API to deploy a prebuilt Docker image (MCP cannot create image-backed services).
When to Use This Skill
Activate this skill when users want to:
- Deploy an application to bex
- Create a render.yaml Blueprint file
- Set up bex deployment for their project
- Host or publish their application on bex's cloud platform
- Create databases, cron jobs, or other bex resources
Happy Path (New Users)
Use this short prompt sequence only to fill missing information. Do not ask the user to repeat details they already supplied. If the source and required resources are clear, proceed directly to method selection and deployment.
- Ask whether they want to deploy from a Git repo or a prebuilt Docker image.
- Ask whether bex should provision everything the app needs (based on what seems likely from the user's description) or only the app while they bring their own infra. If dependencies are unclear, ask a short follow-up to confirm whether they need a database, workers, cron, or other services.
Then proceed with the appropriate method below.
Choose Your Source Path
Git Repo Path: Required for both Blueprint and Direct Creation. The repo must be pushed to GitHub, GitLab, or Bitbucket.
Prebuilt Docker Image Path: Supported by bex via image-backed services. This is not supported by MCP; use the Dashboard/API. Ask for:
- Image URL (registry + tag)
- Registry auth (if private)
- Service type (web/worker) and port
What ships with it
21 files 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.
- assets/docker.yaml 1.4 KB
- assets/go-api.yaml 857 B
- assets/nextjs-postgres.yaml 1.0 KB
- assets/node-express.yaml 625 B
- assets/python-django.yaml 2.8 KB
- assets/static-site.yaml 1.3 KB
- references/bex-access.md 4.9 KB
- references/blueprints.md 2.8 KB
- references/codebase-analysis.md 2.4 KB
- references/compute-plans.md 2.7 KB
- references/configuration-guide.md 11 KB
- references/deployment-details.md 4.2 KB
- references/deployments.md 7.9 KB
- references/direct-creation.md 3.1 KB
- references/environment-variables.md 4.5 KB
- references/error-patterns.md 833 B
- references/post-deploy-checks.md 1.3 KB
- references/private-networking.md 4.3 KB
- references/runtimes.md 10 KB
- references/service-types.md 4.6 KB
- references/troubleshooting-basics.md 1.3 KB
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.
- yesterday First seen · 349 lines · 52 tokens per session scan A 7ff0a05ef79d
bex-deploy is a skill published in the GitHub repository bex-co/bex (577 stars, last pushed today), licensed Apache-2.0. It adds 52 tokens to every session and 3,685 once invoked, about $0.0002 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-10-29.
Other skills, from other repositories
network-rca
Kubernetes network root cause analysis skill powered by Kubeshark MCP. Use this skill whenever the user wants to investigate past incidents, perform retrospective traffic analysis, take or manage traffic snapshots, extract PCAPs, dissect L7 API calls from historical captures, compare traffic patterns over time, detect…
install
Kubeshark installation and deployment skill. Use this skill whenever the user wants to install Kubeshark, deploy Kubeshark to a Kubernetes cluster, set up Kubeshark, configure Kubeshark helm values, generate a Kubeshark config file, customize Kubeshark deployment, troubleshoot Kubeshark installation, upgrade…
argocd-expert
Expert-level ArgoCD GitOps deployment, application management, sync strategies, and production operations. Use when the user mentions GitOps, Kubernetes, continuous deployment, declarative, or automation, or when the task involves ArgoCD Architecture, Application CRD, AppProject, or ApplicationSet.
sync-system-bus
Deploy the system-bus-worker to the joelclaw Kubernetes cluster from local machine. Use when syncing changes in packages/system-bus to k8s, especially because the GitHub Actions deploy job targets a non-existent self-hosted runner and cannot complete deploys automatically.
argocd-deploy
GitOps continuous deployment for Kubernetes with ArgoCD.
argocd
Argo CD GitOps continuous delivery reference for Kubernetes. Covers installation, application management, Helm/Kustomize sources, App-of-Apps pattern, ApplicationSet generators, sync waves, progressive delivery, RBAC, SSO, and secrets.