What is fly-scaffold-app?

A command that creates the starting files for a Fly.io application, including deployment configuration, a container build file, and a GitHub Actions deployment workflow. It can also prepare optional database, object-storage, and cache setup.

Use it to scaffold a new Fly.io project, configure one or more regions, create a safer multi-stage container build, set up automated deployment, and optionally prepare Fly Postgres, Tigris object storage, or Fly Redis.

It removes the repetitive setup work involved in preparing an application for Fly.io while recording sensible defaults that can be adjusted later. It also prompts for key choices such as language, framework, regions, and data services.

fly-scaffold-app — Command for Claude Code by jsgerman-oss

Install

Getting it into your agent

It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.

Clone the repo

git clone --depth 1 https://github.com/jsgerman-oss/blackrim-nimbus-skills

agentmods

npx agentmods add commands/jsgerman-oss/blackrim-nimbus-skills/fly-scaffold-app

Made for: Claude Code.

Or install cloud-fly, the plugin that ships this one along with the rest of its 5 skills, 1 command, 2 agents.

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/commands/jsgerman-oss/blackrim-nimbus-skills/fly-scaffold-app/github.svg)](https://agentmods.dev/commands/jsgerman-oss/blackrim-nimbus-skills/fly-scaffold-app)

Your own site

<a href="https://agentmods.dev/commands/jsgerman-oss/blackrim-nimbus-skills/fly-scaffold-app"><img src="https://agentmods.dev/badge/commands/jsgerman-oss/blackrim-nimbus-skills/fly-scaffold-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.

Your own site · 80×15

<a href="https://agentmods.dev/commands/jsgerman-oss/blackrim-nimbus-skills/fly-scaffold-app"><img src="https://agentmods.dev/badge/commands/jsgerman-oss/blackrim-nimbus-skills/fly-scaffold-app.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 39 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 2,456 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.

Model	Per session	Once invoked
Fable 5.1	$0.00039	$0.02456
Opus 5	$0.00019	$0.01228
Sonnet 5	$0.00008	$0.00491
Haiku 4.5	$0.00004	$0.00246

Measured 12d ago against content hash 4b1ce953ecbd, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

fly-scaffold-app 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 12d 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.

cloud-fly/commands/fly-scaffold-app.md · 286 lines

How it starts

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

Fly Scaffold App

Scaffold a new Fly.io application for a workload described as: $ARGUMENTS

What to do

Confirm app requirements. Ask up to three clarifying questions if not obvious from the description:
- What is the primary programming language and framework?
- Which regions should the app target? (e.g., iad for US East, lhr for Europe, nrt for Asia)
- Does the app need a database (Fly Postgres), object storage (Tigris bucket), or a cache (Fly Redis)?
Do not wait for every detail. Make sensible defaults and document them. The user can adjust fly.toml after scaffold.
Confirm scope with one focused question if state is involved:
- For stateful workloads: is a single primary region acceptable, or does the app need multi-region writes with fly-replay routing?
Generate the project skeleton in the current working directory (or a subdirectory the user specifies). Every scaffold must include:
- A fly.toml with production-grade defaults (see below).
- A Dockerfile appropriate for the language (multi-stage build, non-root user, no secrets in layers).
- A .github/workflows/deploy.yml using superfly/flyctl-actions with a pinned flyctl version and a deploy token (FLY_API_TOKEN).
- A scripts/bootstrap-secrets.sh that documents which secrets to set and provides fly secrets set commands with placeholder values.
- A scripts/setup-postgres.sh (if Postgres is requested) that creates a least-privilege app user.
- A .gitignore appropriate for the language.
- A README.md with bootstrap + deploy + rollback commands.
Wire production-grade defaults. Do not generate demo-grade code:
- HTTPS only: force_https = true on port 80.
- No secrets in fly.toml or Dockerfile. All sensitive values use fly secrets.
- Health check defined with grace_period, interval, and timeout.
- auto_stop_machines = "stop" for stateless services. Note where min_machines_running = 1 is recommended.
- Deploy strategy: bluegreen for production, rolling for staging.
- Image tagged by git SHA in the deploy workflow, not :latest.

Read the full file on GitHub · 286 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.

12d ago First seen · 286 lines · 39 tokens per session scan A 4b1ce953ecbd

Subscribe to this mod's changes

fly-scaffold-app is a command published in the GitHub repository jsgerman-oss/blackrim-nimbus-skills (8 stars, last pushed 26d ago), licensed MIT. It adds 39 tokens to every session and 2,456 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-31.

CI and CD Containers DevOps and cloud

fly-scaffold-app

Getting it into your agent

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

Fly Scaffold App

What to do

What this file has done since we first saw it

Other commands, from other repositories

ops-k8s

arckit.devops

sparc-devops

cost-optimize

sdlc-deploy

sparc-devops