app-backend

app-backend is a skill for Claude Code from ryan-haver/fusebase-mcp. It costs 92 tokens per session (12,070 once invoked), scanned A, a copy of app-backend, MIT.

A guide to adding a backend layer to Fusebase Apps, including server-side APIs and scheduled jobs.

In plain words
What is it for?
It helps set up backend folders, add REST endpoints or WebSockets, and schedule recurring jobs with cron.
Why use it?
It helps when the built-in dashboard interface is not enough and the app needs server-side processing or communication.

Skill for Claude Code

Written for Claude Code: installed under .claude/.

Part of the fusebase plugin — 16 skills, 2 agents, 1 hook, 1 MCP server shipped together

Good fit It helps set up backend folders, add REST endpoints or WebSockets, and schedule recurring jobs with cron.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/ryan-haver/fusebase-mcp/app-backend
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.

Any agent
npx skills add ryan-haver/fusebase-mcp --skill app-backend
Clone the repo
git clone --depth 1 https://github.com/ryan-haver/fusebase-mcp

Made for: Claude Code.

Or install fusebase, the plugin that ships this one along with the rest of its 16 skills, 2 agents, 1 hook, 1 MCP server.

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.

agentmods badge for app-backend

README.md
[![agentmods](https://agentmods.dev/badge/skills/ryan-haver/fusebase-mcp/app-backend/github.svg)](https://agentmods.dev/skills/ryan-haver/fusebase-mcp/app-backend)
Your own site
<a href="https://agentmods.dev/skills/ryan-haver/fusebase-mcp/app-backend"><img src="https://agentmods.dev/badge/skills/ryan-haver/fusebase-mcp/app-backend/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.

agentmods 80×15 button for app-backend

Your own site · 80×15
<a href="https://agentmods.dev/skills/ryan-haver/fusebase-mcp/app-backend"><img src="https://agentmods.dev/badge/skills/ryan-haver/fusebase-mcp/app-backend.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 92 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 12,070 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. A grade says what 26 rules found in the file — not that it is safe.
Origin 97% copy Near-identical to another mod 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.1 $0.00092 $0.12070
Opus 5.5 $0.00037 $0.04828
Sonnet 5.5 $0.00018 $0.02414
Haiku 4.5 $0.00009 $0.01207

Measured 3d ago against content hash ffaebccb1ab9, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

app-backend scanned grade A with 1 finding 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 3d 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.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

When the app needs to receive webhooks from a third-party service (Asana, GitHub, Stripe, Monday, etc.), register the subscription with that provider **yourself** as part of the deploy — do not hand the user a `curl` / a
Origin

This is a copy

97% identical to app-backend — 8 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

apps/client-portal-dashboard/.claude/skills/app-backend/SKILL.md · 980 lines

How it starts

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

App Backend

Multi-User Architecture

Apps are always multi-user. The backend serves requests from many users concurrently. Every design decision must account for this.

Per-user vs. shared state:

Storage Scope Use for
httpOnly cookies Per-user (per browser) OAuth tokens, user preferences, session data
Dashboard rows (keyed by user ID) Per-user (persistent) User settings, saved state
Fusebase secrets / env vars Shared (all users) API keys, service-account credentials
In-memory variables Shared (all users, lost on restart) Short-lived caches only

Common mistakes:

  • ❌ Storing a user's OAuth token in an env var or in-memory config → all users share one token
  • ❌ Storing a user's preference in a module-level variable → last user's preference wins for everyone
  • ❌ Using env vars for per-user settings or selections → same value for everyone
  • ❌ Using session/token-derived values (ft:*, JWT pieces, rotating token IDs) as persistent row partition keys
  • ✅ Store per-user data in cookies or dashboard rows keyed by user
  • ✅ Use env vars only for credentials/config shared across all users (e.g. OAuth client ID/secret)

Shared live reads

A page many people sit on must not call the isolated store once per open browser. Read once per backend process and answer the waiting requests from that result. One user action is one runIsolatedStoreSqlBatch; do not run several store calls in parallel for it. An idle page does not poll every 1–2 seconds. Limits: fusebase-gate/references/isolated-sql.md (Connection budget).

Stable key as partition key (required)

For any persisted per-user data, derive the partition key from stable identity only:

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

  1. 3d ago Changed · +4 lines ffaebccb1ab9
  2. 1mo ago First seen · 976 lines · 92 tokens per session scan A 283a6b315332

Subscribe to this mod's changes

app-backend is a skill published in the GitHub repository ryan-haver/fusebase-mcp (8 stars, last pushed 3d ago), licensed MIT. It adds 92 tokens to every session and 12,070 once invoked, about $0.0004 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). It is 97% identical to app-backend, differing in 8 lines, and is treated as a copy.

Related

app-backend compared with skills from other repositories

app-backend next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
app-backendryan-haver/fusebase-mcpSkill83d agoMITA92Claude Code
mem0-oss-to-platformmem0ai/mem0Skill69kyesterdayApache-2.0A217Claude Code, Codex
azure-mgmt-botservice-dotnetmicrosoft/skillsSkill3.2kyesterdayMITA78Claude Code
fastapi-router-pymicrosoft/skillsSkill3.2kyesterdayMITA46Claude Code
dev-runtimelangwatch/langwatchSkill5.0ktodayApache-2.0A172Claude Code
api-designericrisco/rsc-harnessSkill5293d agoMITA105Claude Code, Codex
migrate-segw-to-raparc-mcp/arc-1Skill253todayMITA106Claude Code