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/mcp-gate-debugnpx skills add fusebase-dev/fusebase-flow --skill mcp-gate-debuggit 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.00056 | $0.00697 |
| Opus 5 | $0.00028 | $0.00349 |
| Sonnet 5 | $0.00011 | $0.00139 |
| Haiku 4.5 | $0.00006 | $0.00070 |
Grade A, and why
mcp-gate-debug 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 — 59 lines — stays where its author put it; the contents beside it link to each section on GitHub.
MCP Gate debug summary
Purpose
Close the loop on Gate MCP work: turn friction into specific improvement ideas for:
.claude/skills/fusebase-gate/(especiallySKILL.mdandreferences/*.md)- MCP prompts / tool descriptions (upstream server)
- Local app code only when the issue is clearly client-side misuse
When to run
After you finish (or pause) a coherent batch of Gate MCP tool_call operations — especially:
- Isolated stores —
listIsolatedStores,createIsolatedStore,initIsolatedStoreStage, migration status/apply, row CRUD,queryIsolatedStoreSql, NoSQL equivalents - Org users, tokens, permissions, health/bootstrap when those sessions were rough
If the user only asked a one-line question with no tools, skip this summary unless they ask for it.
Output format (in the conversation)
Keep it scannable:
- Went well — bullets (tools, prompts, docs that helped).
- Friction — wrong assumptions, missing context, repeated
tools_describe, unclear errors, wrongorgId/storeId/stage, migration/drift confusion, permission surprises. - Improvements — ordered by impact. For each idea, prefer:
- Target: file path (e.g.
fusebase-gate/references/isolated-sql-integrator-troubleshooting.md) or “MCP tool X description / prompt Y” - Change: one sentence
- Why: link to the failure you saw
- Target: file path (e.g.
Isolated stores first
When isolated-store tools were used, before proposing doc changes, re-read if needed:
.claude/skills/fusebase-gate/references/isolated-sql.md.claude/skills/fusebase-gate/references/isolated-sql-migration-discipline.md.claude/skills/fusebase-gate/references/isolated-sql-integrator-troubleshooting.md.claude/skills/fusebase-gate/references/isolated-nosql.md(if NoSQL)
The summary should call out:
- Missing playbook steps (status before apply,
dryRun, checksum/version discipline). - Confusion between dev and prod stages.
- Whether
structuredIssues/ drift messaging was understandable.
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 · 59 lines · 56 tokens per session scan A aeb201f0cf55
mcp-gate-debug is a skill published in the GitHub repository fusebase-dev/fusebase-flow (9 stars, last pushed 7d ago), licensed MIT. It adds 56 tokens to every session and 697 once invoked, about $0.0003 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.