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 agentmods add skills/fusebase-dev/fusebase-flow/fusebase-gatenpx skills add fusebase-dev/fusebase-flow --skill fusebase-gategit clone --depth 1 https://github.com/fusebase-dev/fusebase-flowWhat 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 | $0.00038 | $0.01833 |
| Opus 5 | $0.00019 | $0.00916 |
| Sonnet 5 | $0.00008 | $0.00367 |
| Haiku 4.5 | $0.00004 | $0.00183 |
Grade A, and why
fusebase-gate 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 2d 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.
How it starts
The opening of the file, as written. The whole thing — 151 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Fusebase Gate MCP Skill
This document describes how to use MCP (Model Context Protocol) with Fusebase Gate during LLM development. Fusebase Gate is a service consumer built on top of the shared Fusebase platform runtime.
For rules and checklists, see AGENTS.md.
For FuseBase PostgreSQL Database (sql / postgres via the Gate isolated-stores contract), use references/isolated-sql.md for the MCP-oriented sequence and references/isolated-sql-migration-discipline.md whenever you edit or apply migration bundles (anti-drift). For runtime errors and support handoff, use references/isolated-sql-integrator-troubleshooting.md. Do not load operator runbooks (isolated-sql-stores, isolated-sql-rls-plan) — they are platform-internal. See TOC below.
Critical isolated-store runtime rule: a Gate isolated store is a platform-bound resource, not app environment configuration. Do not ask users to create app secrets or env vars for storeId, database IDs, physical database names, or provider connection details. Runtime code must resolve the store through Gate using the app token/source scope and stable alias (or use the store already bound by the platform). storeId may appear in MCP/operator handoff logs or CLI migration commands, but it must not be persisted as an app secret or hardcoded runtime config.
References
Each reference is in a separate file under references/. Load the file when you need that topic.
meta
specialized
- Fusebase Auth For AI Apps
- Fusebase Gate — Isolated SQL migration discipline
- Fusebase Gate App Magic Link Operations
- Fusebase Gate Billing And Stripe Flows
- Fusebase Gate Email Operations
- Fusebase Gate Files Flows
- Fusebase Gate Membership And Portal Flows
- Fusebase Gate Notes Operations
- Fusebase Gate Org Group Operations
- Fusebase Gate Organization URLs
- Fusebase Gate Portals — Create Operations
- Fusebase Gate Portals Operations
- Fusebase Gate Stripe App And Agent Integration
- Fusebase Gate Users Operations
- FuseBase PostgreSQL Database
- FuseBase PostgreSQL Database
- FuseBase PostgreSQL Database — integrator troubleshooting
- Isolated stores hierarchy: Gate vs Neon
- Isolated stores release checklist
- Portal iframe embed context (Gate SQL RLS)
- Portal theme styling (custom CSS override contract)
- Stripe for apps and agents (Gate)
What ships with it
26 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/app-magic-links.md 32 KB
- references/authz.md 2.7 KB
- references/billing.md 4.9 KB
- references/bootstrap.md 4.1 KB
- references/emails.md 2.4 KB
- references/files.md 4.7 KB
- references/fusebase-auth.md 29 KB
- references/isolated-sql-integrator-troubleshooting.md 8.1 KB
- references/isolated-sql-migration-discipline.md 6.0 KB
- references/isolated-sql.md 20 KB
- references/isolated-store-hierarchy.md 9.1 KB
- references/isolated-stores-release-checklist.md 2.5 KB
- references/isolated.md 8.3 KB
- references/membership.md 7.5 KB
- references/notes.md 12 KB
- references/org-groups.md 5.0 KB
- references/orgs.md 2.5 KB
- references/portal-embed-context.md 6.9 KB
- references/portal-theme-variables.md 3.1 KB
- references/portals-create.md 3.9 KB
- references/portals.md 130 KB
- references/sdk.md 8.8 KB
- references/stripe-apps.md 6.4 KB
- references/stripe-for-apps-and-agents.md 14 KB
- references/tooling.md 3.8 KB
- references/users.md 5.2 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.
- 2d ago First seen · 151 lines · 38 tokens per session scan A bf37f49b917e
fusebase-gate is a skill published in the GitHub repository fusebase-dev/fusebase-flow (9 stars, last pushed 7d ago), licensed MIT. It adds 38 tokens to every session and 1,833 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.
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.
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.
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…
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…
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.
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.