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/remote-logsnpx skills add fusebase-dev/fusebase-flow --skill remote-logsgit 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.01121 |
| Opus 5 | $0.00028 | $0.00561 |
| Sonnet 5 | $0.00011 | $0.00224 |
| Haiku 4.5 | $0.00006 | $0.00112 |
Grade A, and why
remote-logs 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 — 155 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Remote Logs
This skill applies only to apps with a backend/ folder. Frontend-only apps do not produce remote logs.
When an app backend has been deployed using fusebase deploy, you can fetch logs from the cloud:
- Build logs - Output from the container image build process
- Runtime logs - Live stdout/stderr and system logs from the running backend
Important Distinction
| Context | Command | What It Reads |
|---|---|---|
| Local development | fusebase dev start |
Log files in <app>/logs/dev-*/ |
| Deployed backend | fusebase remote-logs |
Cloud build and runtime logs |
If the app is running locally via fusebase dev start, use the dev-debug-logs skill instead.
Commands
Build Logs
Fetch build/deployment logs from the most recent deploy:
fusebase remote-logs build <appId>
Output includes:
- Build status (
in_progress,failed,finished) - Full build log (Dockerfile execution, npm install, etc.)
- Deploy job ID for reference
Runtime Logs
Fetch live logs from the running backend:
# Default: last 100 console (stdout/stderr) entries
fusebase remote-logs runtime <appId>
# Specify tail count (0-300)
fusebase remote-logs runtime <appId> --tail 200
# Get system logs instead of console logs
fusebase remote-logs runtime <appId> --type system
# Filter to a specific container (backend or sidecar)
fusebase remote-logs runtime <appId> --container api
fusebase remote-logs runtime <appId> --container my-sidecar
Options:
--tail <n>- Number of log entries (0-300, default: 100)--type <type>- Log type:console(stdout/stderr) orsystem(service/infrastructure logs)--container <name>- Filter logs to a specific container. Useapifor the main backend, or the sidecar name for sidecar containers
Log Format with Sidecars
When an app backend has sidecar containers, runtime logs include output from all containers. Each log line is prefixed with the container name:
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 · 155 lines · 56 tokens per session scan A 551abc90796d
remote-logs 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 1,121 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.