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-blueprintsgit 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-blueprints)<a href="https://agentmods.dev/skills/bex-co/bex/bex-blueprints"><img src="https://agentmods.dev/badge/skills/bex-co/bex/bex-blueprints/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-blueprints"><img src="https://agentmods.dev/badge/skills/bex-co/bex/bex-blueprints.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.00093 | $0.03022 |
| Opus 5.5 | $0.00037 | $0.01209 |
| Sonnet 5.5 | $0.00019 | $0.00604 |
| Haiku 4.5 | $0.00009 | $0.00302 |
Grade A, and why
bex-blueprints 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 — 285 lines — stays where its author put it; the contents beside it link to each section on GitHub.
bex Blueprints (render.yaml)
Blueprints define bex infrastructure as YAML (commonly render.yaml at the repo root). This skill focuses on authoring, wiring, projects/environments, previews, validation, and immutable fields. Heavy detail lives under references/.
Before creating or modifying a Blueprint, read references/blueprints.md for the current specification-fetch, validation, repository-sync, and safety workflow.
For current compute-plan terminology, Plan IDs, and availability, use references/compute-plans.md instead of relying on plan catalogs embedded in examples.
Before adding or changing a service-attached disk, read references/persistent-disks.md for current architectural constraints and configuration workflow.
Before wiring private-network addresses, ports, or discovery hostnames, read references/private-networking.md.
Before choosing a service type or translating its Dashboard name to Blueprint structure, read references/service-types.md.
When to Use
Apply this skill when the user:
- Creates or edits a
render.yaml/ Blueprint - Wires databases, private services, or Key Value into app env vars
- Groups services with projects and environments
- Configures preview environments for pull requests
- Validates YAML against bex’s schema or CLI
- Asks what can or cannot change after a resource is created
For end-to-end deploy flows and MCP/CLI operations, see bex-deploy. For env var strategy outside Blueprint syntax, see bex-env-vars. For Docker-specific Blueprint fields, see bex-docker.
Blueprint Structure
Top-level keys
| Key | Purpose |
|---|---|
services |
Web, worker, cron, private service, Key Value, static (via web + runtime: static) |
databases |
Managed PostgreSQL instances |
envVarGroups |
Reusable env var sets attached to services |
projects |
Optional grouping; contains environments and service lists |
previews |
Defaults for PR preview environments |
What ships with it
10 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.
- references/blueprints.md 2.8 KB
- references/common-mistakes.md 4.5 KB
- references/compute-plans.md 2.3 KB
- references/environment-variables.md 4.5 KB
- references/field-reference.md 8.7 KB
- references/persistent-disks.md 3.7 KB
- references/preview-environments.md 4.8 KB
- references/private-networking.md 4.3 KB
- references/service-types.md 4.6 KB
- references/wiring-patterns.md 3.7 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 · 285 lines · 93 tokens per session scan A f5724b8c951b
bex-blueprints is a skill published in the GitHub repository bex-co/bex (577 stars, last pushed today), licensed Apache-2.0. It adds 93 tokens to every session and 3,022 once invoked, about $0.0004 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.