bun:deploy

bun:deploy is a command for Claude Code from secondsky/claude-skills. It costs 10 tokens per session (980 once invoked), scanned A, original, MIT.

A deployment guide for Bun applications, where Bun is a JavaScript runtime and toolkit. It shows how to package and publish an app using Docker, Cloudflare Workers, Vercel, Fly.io, and Railway.

In plain words
What is it for?
Use it when preparing a Bun app for Docker or one of the listed cloud hosting platforms. It helps create deployment files, build the app, and run the platform's deployment command.
Why use it?
It removes the need to work out platform-specific configuration and deployment commands from scratch. It gives you starting files and commands for putting a Bun app into production.

Command for Claude Code

Written for Claude Code: arguments in frontmatter.

Part of the bun plugin — 27 skills, 6 commands, 3 agents, 2 hooks shipped together

Good fit Use it when preparing a Bun app for Docker or one of the listed cloud hosting platforms. It helps create deployment files, build the app, and run the platform's deployment command.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/secondsky/claude-skills/bun-deploy
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.

Clone the repo
git clone --depth 1 https://github.com/secondsky/claude-skills

Made for: Claude Code.

Or install bun, the plugin that ships this one along with the rest of its 27 skills, 6 commands, 3 agents, 2 hooks.

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.

agentmods badge for bun:deploy

README.md
[![agentmods](https://agentmods.dev/badge/commands/secondsky/claude-skills/bun-deploy/github.svg)](https://agentmods.dev/commands/secondsky/claude-skills/bun-deploy)
Your own site
<a href="https://agentmods.dev/commands/secondsky/claude-skills/bun-deploy"><img src="https://agentmods.dev/badge/commands/secondsky/claude-skills/bun-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.

agentmods 80×15 button for bun:deploy

Your own site · 80×15
<a href="https://agentmods.dev/commands/secondsky/claude-skills/bun-deploy"><img src="https://agentmods.dev/badge/commands/secondsky/claude-skills/bun-deploy.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 10 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 980 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00010 $0.00980
Opus 5.5 $0.00004 $0.00392
Sonnet 5.5 $0.00002 $0.00196
Haiku 4.5 $0.00001 $0.00098

Measured 1mo ago against content hash a06b542fa741, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

bun:deploy 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 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.

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.

plugins/bun/commands/bun-deploy.md · 217 lines

How it starts

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

Bun Deployment

Deploy Bun applications to production environments.

Supported Platforms

Docker

Create optimized Dockerfile:

FROM oven/bun:1 AS builder
WORKDIR /app
COPY package.json bun.lockb ./
RUN bun install --frozen-lockfile
COPY . .
RUN bun run build

FROM oven/bun:1-slim
WORKDIR /app
COPY --from=builder /app/dist ./dist
COPY --from=builder /app/node_modules ./node_modules
COPY package.json ./
USER bun
EXPOSE 3000
CMD ["bun", "run", "dist/index.js"]

Commands:

docker build -t myapp .
docker run -p 3000:3000 myapp

Cloudflare Workers

Update wrangler.toml:

name = "my-worker"
main = "src/index.ts"
compatibility_date = "2024-01-01"

Deploy:

bun run build
bunx wrangler deploy

Vercel

Add vercel.json:

{
  "buildCommand": "bun run build",
  "installCommand": "bun install",
  "framework": null
}

Deploy:

bunx vercel

Fly.io

Create fly.toml:

app = "my-app"
primary_region = "ord"

[build]
  dockerfile = "Dockerfile"

[http_service]
  internal_port = 3000
  force_https = true

[[services.ports]]
  handlers = ["http"]
  port = 80

[[services.ports]]
  handlers = ["tls", "http"]
  port = 443

Deploy:

fly deploy

Railway

Railway auto-detects Bun projects. Add:

{
  "scripts": {
    "start": "bun run src/index.ts"
  }
}

Deploy via Railway CLI or GitHub integration.

Pre-Deployment Checklist

  1. Build passes - bun run build
  2. Tests pass - bun test
  3. Environment variables - All secrets configured
  4. Health check - /health endpoint exists
  5. Logging - Structured logging configured
  6. Error handling - Global error handlers
  7. Security headers - CORS, CSP configured
  8. Database migrations - Applied if needed

Environment Configuration

# Generate .env.example from .env
grep -v '^#' .env | sed 's/=.*/=/' > .env.example

# Required variables
DATABASE_URL=
API_SECRET=
NODE_ENV=production

Read the full file on GitHub · 217 lines

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.

  1. 1mo ago First seen · 217 lines · 10 tokens per session scan A a06b542fa741

Subscribe to this mod's changes

bun:deploy is a command published in the GitHub repository secondsky/claude-skills (232 stars, last pushed yesterday), licensed MIT. It adds 10 tokens to every session and 980 once invoked, about $0.0000 per session on Opus 5.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.