What is bex-migrate-from-heroku?

A workflow for moving an application from Heroku to bex. Heroku is a cloud platform for running applications; the workflow reads files such as a Procfile and dependency files to work out the services and settings to recreate.

Use it to inventory a Heroku app, generate an equivalent bex plan or Blueprint, optionally create services, and check the migration.

It reduces the manual work of translating a Heroku app's process, dependencies, and configuration into bex services. It can use supplied project details and, when available, live Heroku or bex access to fill gaps and verify the result.

bex-migrate-from-heroku — Skill for Claude Code and Codex by bex-co

Install

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.

Any agent

npx skills add bex-co/bex --skill bex-migrate-from-heroku

Clone the repo

git clone --depth 1 https://github.com/bex-co/bex

Made for: Claude Code, Codex.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/bex-co/bex/bex-migrate-from-heroku/github.svg)](https://agentmods.dev/skills/bex-co/bex/bex-migrate-from-heroku)

Your own site

<a href="https://agentmods.dev/skills/bex-co/bex/bex-migrate-from-heroku"><img src="https://agentmods.dev/badge/skills/bex-co/bex/bex-migrate-from-heroku/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/bex-co/bex/bex-migrate-from-heroku"><img src="https://agentmods.dev/badge/skills/bex-co/bex/bex-migrate-from-heroku.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 105 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 4,778 The whole file, excluding the scripts and references it only reads on demand.

Security scan C 2 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00105	$0.04778
Opus 5.5	$0.00042	$0.01911
Sonnet 5.5	$0.00021	$0.00956
Haiku 4.5	$0.00011	$0.00478

Measured yesterday against content hash 20f4ea6a812d, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade C, and why

bex-migrate-from-heroku scanned grade C with 2 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 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.

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.

- Linux/macOS: `curl -fsSL https://raw.githubusercontent.com/bex-co/bex/main/scripts/install-bex.sh | sh`

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

- Linux/macOS: `curl -fsSL https://raw.githubusercontent.com/bex-co/bex/main/scripts/install-bex.sh | sh`

lego/cli/internal/skills/pack/skills/bex-migrate-from-heroku/SKILL.md · 334 lines

How it starts

The opening of the file, as written. The whole thing — 334 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Heroku to bex Migration

Migrate from Heroku to bex using the user's supplied inventory or local project files, then optionally enrich missing details with live Heroku data via MCP.

Prerequisites Check

Before starting, verify what's available:

App inventory (required) — use complete details supplied by the user, or inspect local project files such as Procfile, app.json, package.json, requirements.txt, Gemfile, or go.mod
bex MCP (recommended) — check if list_services tool is available. Required for MCP Direct Creation (Step 3B) and automated verification (Step 6). Not required for the Blueprint path — the bex CLI and Dashboard handle generation, validation, and deployment.
Heroku MCP (optional) — check if list_apps tool is available

Do not require local files or MCP when the user has already supplied enough information for the requested plan, Blueprint, or migration instructions. If bex MCP is missing and the user actually needs live bex access, use the bex access workflow in references/bex-access.md; the MCP setup guide adds Heroku-specific setup. If Heroku MCP is missing, use supplied values or ask only for missing config-var names and add-on details.

Migration Workflow

For an end-to-end migration, execute the applicable steps in order. Present findings to the user and get confirmation before creating any resources.

Before mapping Heroku process types to bex service types, read references/service-types.md.

Choose the narrow workflow

Complete inventory + Blueprint request: read references/service-mapping.md, references/blueprint-example.md, and references/blueprints.md; generate the complete Blueprint directly. Do not call live tools merely to rediscover values the user supplied.
Single-service migration: gather the missing inventory, present the plan, and use MCP Direct Creation only after the user asks to create the service and confirms the plan.
Data-migration question: read references/service-mapping.md and references/data-migration.md; provide the applicable procedure without performing live operations unless requested.

Read the full file on GitHub · 334 lines

Files

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.

Changes

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 · 334 lines · 105 tokens per session scan C 20f4ea6a812d

Subscribe to this mod's changes

bex-migrate-from-heroku is a skill published in the GitHub repository bex-co/bex (577 stars, last pushed today), licensed Apache-2.0. It adds 105 tokens to every session and 4,778 once invoked, about $0.0004 per session on Opus 5.5. A static security scan graded it C with 2 findings (downloads and executes remote code, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-10-29.

Cloud DevOps and cloud Go deploy gitops hetzner kubernetes kubernetes-operator

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…

kubeshark/kubeshark · 163 tokens

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…

kubeshark/kubeshark · 257 tokens

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.

personamanagmentlayer/pcl · 65 tokens

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.

joelhooks/joelclaw · 60 tokens

argocd-deploy

GitOps continuous deployment for Kubernetes with ArgoCD.

bidewio/better-openclaw · 16 tokens

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.

bytesagain/ai-skills · 52 tokens

bex-migrate-from-heroku