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/app-business-docsnpx skills add fusebase-dev/fusebase-flow --skill app-business-docsgit 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.00048 | $0.00601 |
| Opus 5 | $0.00024 | $0.00300 |
| Sonnet 5 | $0.00010 | $0.00120 |
| Haiku 4.5 | $0.00005 | $0.00060 |
Grade A, and why
app-business-docs 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 — 51 lines — stays where its author put it; the contents beside it link to each section on GitHub.
App business logic documentation (English)
Purpose
Keep a single English narrative so humans (and future LLM turns) can understand what the app does and why, without reading every file.
Canonical file: docs/en/business-logic.md
Create docs/en/ if it does not exist.
When to use this skill
- After business-logic changes — routes, validation, state machines, permissions, multi-step flows, integrations, or copy that reflects real rules.
- Revalidation — the user asks to refresh the doc from the codebase, or debugging shows the doc (or mental model) is wrong or stale.
- Onboarding — initial fill after an app or app reaches a coherent shape.
Do not treat this as API reference: no exhaustive endpoint lists unless they carry domain meaning. Prefer flows, invariants, and “if user does X then Y”.
Document structure (adapt as needed)
Use clear headings, for example:
- Product overview — who uses it, primary job-to-be-done.
- Glossary — domain terms.
- Actors & roles — visitor, member, admin, system, etc., aligned with real authz.
- Main scenarios — numbered happy paths (step-by-step).
- Edge cases & failure behavior — errors, empty states, retries, idempotency.
- Data & ownership — what lives in dashboards vs Gate vs isolated stores (if any), at a conceptual level.
- Code map — short table: scenario or area → primary paths (
apps/...,backend/...).
Workflow
- Read the current
docs/en/business-logic.mdif present. - Inspect the code that implements the changed or unclear behavior (apps,
backend/, shared libs). - Update the doc so it matches observable behavior, not intentions that are not implemented.
- If behavior is ambiguous, state the ambiguity and what you verified in code or runtime.
Quality bar
- Short paragraphs, concrete examples, no filler.
- A new teammate should follow main scenarios without opening the repo.
- When revalidating during debug, add a “Debugging notes” subsection with dated bullets if it helps (optional).
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 · 51 lines · 48 tokens per session scan A 2f6595f0dfdf
app-business-docs is a skill published in the GitHub repository fusebase-dev/fusebase-flow (9 stars, last pushed 7d ago), licensed MIT. It adds 48 tokens to every session and 601 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.