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/bex-co/bex/mock-clusternpx skills add bex-co/bex --skill mock-clustergit 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/mock-cluster)<a href="https://agentmods.dev/skills/bex-co/bex/mock-cluster"><img src="https://agentmods.dev/badge/skills/bex-co/bex/mock-cluster.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.00048 | $0.00987 |
| Opus 5 | $0.00024 | $0.00494 |
| Sonnet 5 | $0.00010 | $0.00197 |
| Haiku 4.5 | $0.00005 | $0.00099 |
Grade A, and why
mock-cluster scanned grade A with 0 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 5d 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.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
Bring up the local mock of the Hetzner substrate and deploy the bex operator into it.
If $ARGUMENTS is scale N: just run bash scripts/mock-cluster.sh scale N, then show kubectl get nodes (with KUBECONFIG=infra/local/bex.kubeconfig) and stop.
Otherwise, run the full bring-up:
bash scripts/mock-cluster.sh— kind infra cluster + Cluster API + CAPD app cluster, plus the app-cluster baseline the operator needs: Calico, coredns/calico-kube-controllers control-plane pins, local-path default StorageClass, cert-manager (prod's pinned version;make deploy's webhook cert requires it). This can take several minutes; it writes the app-cluster kubeconfig toinfra/local/bex.kubeconfig.- Use that kubeconfig for every following command:
export KUBECONFIG=$PWD/infra/local/bex.kubeconfig(or--kubeconfig). Never print its contents. - Build and load the operator image (CAPD nodes can't pull local-only images):
( cd lego/operator && make docker-build IMG=bex-operator:dev )docker save bex-operator:dev -o /tmp/bex-op.tar- For each node (strip the
node/prefix —kubectl get nodes -o namereturnsnode/<name>butdocker cp/docker execneed the bare container name):for n in $(kubectl get nodes -o name | cut -d/ -f2); do docker cp /tmp/bex-op.tar "$n":/op.tar && docker exec "$n" ctr -n k8s.io images import /op.tar done
( cd lego/operator && make deploy IMG=bex-operator:dev )— deploys to nsbex-systemwithBEX_RUNTIME=kubernetes. Thebex-ssh-gatewayIngressRouteTCP fails without Traefik CRDs — expected and harmless on the mock; everything else applies. Thenkubectl apply -f deploy/gitops/base/operator-apps-rbac.yaml— the apps-namespacebex-operator-appsRole/RoleBinding is Argo-managed in prod and absent from the operator's kustomize config; without it the manager crashloops on "failed to wait for … caches to sync" (its namespace-scoped Secret/Job watches indefaultare forbidden; w1/043).- Local-CAPD-only fixes (re-apply all three after every
make deploy— it reverts them; w1/043):- Label the control-plane node into the platform pool (the manifest's nodeSelector is
bex.co/pool=platform, and the operator must sit on the control-plane node because OrbStack/Calico can't route cross-node pod→apiserver; see docs/ADR004-app-deployment.md):kubectl label node <control-plane-node> bex.co/pool=platform --overwrite - Pin the operator to the control-plane node:
kubectl -n bex-system patch deploy bex-controller-manager --type merge -p \ '{"spec":{"template":{"spec":{"nodeSelector":{"node-role.kubernetes.io/control-plane":""}, "tolerations":[{"key":"node-role.kubernetes.io/control-plane","effect":"NoSchedule"}]}}}}' - The manifest sets
imagePullPolicy: Always, which can never be satisfied by the ctr-imported local image (ErrImagePull) — override it:kubectl -n bex-system patch deploy bex-controller-manager --type strategic -p \ '{"spec":{"template":{"spec":{"containers":[{"name":"manager","imagePullPolicy":"IfNotPresent"}]}}}}'
- Label the control-plane node into the platform pool (the manifest's nodeSelector is
kubectl -n bex-system rollout status deploy/bex-controller-manager— wait for Ready.
Finish by reporting: node list, operator pod status, and the one-liners to deploy an App (/deploy-app) and to scale machines (/mock-cluster scale N).
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.
- 5d ago First seen · 44 lines · 48 tokens per session scan A 6eb164b22fb9
mock-cluster is a skill published in the GitHub repository bex-co/bex (420 stars, last pushed today), licensed Apache-2.0. It adds 48 tokens to every session and 987 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
gen-test
Generate idiomatic tests for Go packages and handlers in the Meshery project.
bump-go-version
Bumps the Go version to the latest release across go.mod, tools.mod, and Dockerfiles.
project-writing-go-modules-framework-v2
Use when creating or migrating a Go go.d collector to framework V2, touching CollectorV2, metrix.CollectorStore, ChartTemplateYAML/charts.yaml, charttpl/chartengine, V2 host scopes/vnodes, or V2 collector tests. Focuses on concise maintainer-preferred V2 collector patterns.
project-go-collector-design
Early design decisions for Go go.d collectors, made before code. Use when designing a new go.d collector; when adding, renaming, removing, or changing the default of a config option or mode; when adding or changing a Function; when changing what a metric means or which entities become charts or vnodes; when a…
mariadb-operator-pr-review
Perform a structured maintainer-style PR review for the mariadb-operator repository. Gathers PR context, triages the change, and evaluates correctness, safety, pitfalls, backwards compatibility and code quality against the project conventions documented in AGENTS.md. Use whenever the user mentions a mariadb-operator…
mariadb-operator-comment
Post a comment (or a formal PR review) to a GitHub issue or pull request in mariadb-operator/mariadb-operator. Use whenever the user wants to publish something to GitHub for this repo — "comment on issue #123", "post this as a PR comment", "leave a note on #456", "reply on the PR" — and especially when they want the…