Borrowing it
Nothing to install: this file belongs to bex-co/bex. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/bex-co/bex/main/.claude/skills/deploy-app/SKILL.mdgit 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/deploy-app)<a href="https://agentmods.dev/skills/bex-co/bex/deploy-app"><img src="https://agentmods.dev/badge/skills/bex-co/bex/deploy-app/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/deploy-app"><img src="https://agentmods.dev/badge/skills/bex-co/bex/deploy-app.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 3 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Privilege Escalation · line 10 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
- high Privilege Escalation · line 10 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
- high Tool Misuse · line 16 Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).Fix: Validate all tool parameters against an allowlist. Reject dangerous parameter values (shell=True, --force, -rf /) and use safe defaults.
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.00056 | $0.00566 |
| Opus 5.5 | $0.00022 | $0.00226 |
| Sonnet 5.5 | $0.00011 | $0.00113 |
| Haiku 4.5 | $0.00006 | $0.00057 |
Grade A, and why
deploy-app 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.
allowed-tools: Bash(kubectl:*), Bash(bash scripts/app-apply.sh:*), Bash(curl:*), Bash(jq:*) What it actually says
Deploy an App and verify it end-to-end. Use KUBECONFIG=infra/local/bex.kubeconfig if no other cluster is targeted.
Requires BEX_API_URL and BEX_API_TOKEN in the environment (scripts/app-apply.sh reads them and fails with set BEX_API_URL if unset — both are client-supplied, not in .env.example; BEX_API_PUBLIC_URL in .env.example is the unrelated backend DeployHook origin). BEX_API_TOKEN is the Hydra-issued Bearer token (API key minted via /v1/api-keys), not the removed static shared secret. Optional BEX_OWNER_ID, BEX_REPO, BEX_BRANCH narrow the deploy.
- If
$ARGUMENTSis a path to arender.yaml(or legacybex.ymlalias — canonical isrender.yaml, seescripts/app-apply.sh), apply it withDRY_RUN=1 bash scripts/app-apply.sh $ARGUMENTSfirst and show the generated App CR, thenbash scripts/app-apply.sh $ARGUMENTSto deploy. If$ARGUMENTSis a directory, pass the directory — the script discoversrender.yamlthenbex.ymlinside it. Otherwise apply the sample:kubectl apply -f examples/whoami-app.yaml. - Watch until ready: poll
kubectl get apps.app.bex.co <name> -o jsonpath='{.status.phase} {.status.revision} {.status.url}'until phase isReady(timeout ~3 minutes; on timeout, showkubectl describe apps.app.bex.co <name>and the operator logskubectl -n bex-system logs deploy/bex-controller-manager --tail=50). - If
status.urlis set and resolvable,curl -fsSit (use--resolve/-konly if the local mock has no real DNS/TLS) and show the response status. - Report: App name, phase, revision, url, and where the pods landed (
kubectl get pods -l app.bex.co/app=<name> -o wide).
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.
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 · 18 lines · 56 tokens per session scan A 76fe692aec21
deploy-app is a skill published in the GitHub repository bex-co/bex (574 stars, last pushed today), licensed Apache-2.0. It adds 56 tokens to every session and 566 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-08-30.
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…
kfl
KFL2 (Kubeshark Filter Language) reference. This skill MUST be loaded before writing, constructing, or suggesting any KFL filter expression. KFL is statically typed — incorrect field names or syntax will fail silently or error. Do not guess at KFL syntax without this skill loaded. Trigger on any mention of KFL, CEL…
security-audit
Kubernetes network security audit skill powered by Kubeshark MCP. Use this skill whenever the user wants to audit a cluster for security threats, detect compromised workloads, find malicious traffic patterns, hunt for indicators of compromise (IOCs), check for data exfiltration, identify C2 (command and control)…
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.
epistemic-graph-deploy
Promote and deploy the epistemic-graph engine (the SI-native database) in the live Kubernetes graph-os unified-image deployment, and restart its clients safely. Use when shipping a new engine build, rolling out Rust-side changes, or restarting graph-os and messaging to pick up a validated artifact. The engine is baked…