fusebase-cli

A guide for using the Fusebase command-line tool to create, configure, run, and deploy Fusebase Apps.

In plain words
What is it for?
Use it to initialize Fusebase projects, manage them during development, deploy them, and configure permissions for dashboards.
Why use it?
Without a consistent process, app setup, authentication, local development, and deployment can be easy to misconfigure.

Skill for Claude CodeCodex

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.

agentmods
npx agentmods add skills/fusebase-dev/fusebase-flow/fusebase-cli
Any agent
npx skills add fusebase-dev/fusebase-flow --skill fusebase-cli
Clone the repo
git clone --depth 1 https://github.com/fusebase-dev/fusebase-flow

Made for: Claude Code, Codex.

Per session 72 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 10,330 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00072 $0.10330
Opus 5 $0.00036 $0.05165
Sonnet 5 $0.00014 $0.02066
Haiku 4.5 $0.00007 $0.01033

Measured yesterday against content hash cbf0c333b372, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

fusebase-cli 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 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.

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.

.agents/skills/fusebase-cli/SKILL.md · 810 lines

How it starts

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

Fusebase CLI (fusebase)

This skill describes how to use the Fusebase CLI tool to manage and deploy Fusebase Apps apps.

For environment migrations, pair this skill with the local project guides App Environments Guide and App Environment Migration Guide. When e2e tests are part of the work, also load skill app-e2e-tests and local guide E2E Playwright Setup Guide; when backend runtime env or Gate access is involved, also load app-backend and fusebase-gate as applicable.

Overview

The Fusebase CLI (fusebase) is a command-line tool for:

  • Initializing new Fusebase Apps projects
  • Managing app development with hot reload
  • Deploying apps to the Fusebase platform

Installation & Authentication

The fusebase CLI is installed globally. Always invoke it as fusebase <command>never use npx fusebase.

Before using the CLI, authenticate with your API key:

fusebase auth

This stores credentials in ~/.fusebase/config.json.

Project Configuration (fusebase.json)

Every Fusebase Apps project requires a fusebase.json file in the project root. This file defines the app and its apps.

For details on the fusebase.json schema, see references/fusebase-json-schema.md.

Declarative manifest — never invent an app id

apps[] is declarative: an app entry carries subdomain + name and omits the platform app id. fusebase deploy reconciles each entry against the platform — it binds to the app with a matching subdomain, or creates it if missing. The product id (productId) is always required; only the per-app id is omitted.

⚠️ Never invent or hand-write an apps[].id. The platform owns app ids. Writing your own id and then running fusebase app create causes a double-registration conflict — the platform creates a brand-new app whose id no longer matches the one you wrote. Add a declarative record (no id) and run fusebase deploy (or fusebase app create); old apps that already carry a real id keep working unchanged.

Read the full file on GitHub · 810 lines

Files

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.

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. yesterday First seen · 810 lines · 72 tokens per session scan A cbf0c333b372

Subscribe to this mod's changes

fusebase-cli is a skill published in the GitHub repository fusebase-dev/fusebase-flow (9 stars, last pushed 6d ago), licensed MIT. It adds 72 tokens to every session and 10,330 once invoked, about $0.0004 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.

Related

Other skills, from other repositories

adobe-express-core

Adobe Express environment essentials, two-runtime architecture, project setup, and MCP server configuration. Use when starting add-on development, understanding iframe vs sandbox boundaries, configuring MCP servers, setting up local projects, or validating manifest configuration.

Sandgrouse/adobe-express-dev-skill · 50 tokens

adobe-express-monetization

Monetize Adobe Express add-ons with subscriptions and payments. Use when designing checkout flows, defining subscription tiers, implementing webhook verification, managing entitlements, or securing backend billing logic.

Sandgrouse/adobe-express-dev-skill · 44 tokens

adobe-express-spectrum-ui-ux

Build or review Adobe Express add-on panel UI with Spectrum patterns, stack selection guidance (raw SWC, swc-react, React Spectrum), Express theme setup, state and navigation design, and actionable UX quality checks. Use when implementing or auditing panel layouts, interaction states, multi-screen flows, and…

Sandgrouse/adobe-express-dev-skill · 70 tokens

adobe-express-cors-and-backend

Diagnose and fix CORS errors between Adobe Express add-on UI and backend APIs across local development, private listing, and public listing stages. Use when browser requests fail with preflight, Access-Control-Allow-Origin, Access-Control-Allow-Headers, or OPTIONS issues; when moving from localhost to hosted add-on…

Sandgrouse/adobe-express-dev-skill · 92 tokens

adobe-express-document-manipulation

Create and modify document content in Adobe Express add-ons using Document SDK. Use when planning document operations, inserting shapes/text/media, sequencing sandbox commands, or troubleshooting document edits.

Sandgrouse/adobe-express-dev-skill · 43 tokens

adobe-express-oauth-authentication

Implement OAuth 2.0 and authentication flows for Adobe Express add-ons. Use when connecting to cloud providers (Dropbox, OneDrive, Google Drive), managing tokens, storing credentials, or designing login surfaces.

Sandgrouse/adobe-express-dev-skill · 50 tokens