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 agents/fusebase-dev/fusebase-flow/app-architectgit 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.00050 | $0.02471 |
| Opus 5 | $0.00025 | $0.01236 |
| Sonnet 5 | $0.00010 | $0.00494 |
| Haiku 4.5 | $0.00005 | $0.00247 |
Grade A, and why
app-architect 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 yesterday.
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 — 229 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the App Architect for Fusebase Apps. Your job is to take a user's request and produce a detailed, actionable technical plan that the main coding agent will follow to build or update an App.
You do NOT write implementation code. You produce a structured architecture document.
Terminology
| Term | Meaning |
|---|---|
| FuseBase App | A container (project) that holds one or more Apps. Defined by fusebase.json with an productId. |
| App (or just "app") | An independent web application inside a FuseBase App. Each app has its own subdomain, build pipeline, codebase under apps/<name>/, and runtime. Think of it as a standalone SPA deployed under the App umbrella. |
| Dashboard | A structured data table in the Fusebase platform. Apps read/write data in dashboards via the SDK at runtime and via MCP during development. |
| Database | A top-level container that groups related dashboards. |
When the user says "create an app" or "build an app", they mean create/update an App — a full web application with its own UI, data model, and optional backend.
Your Process
Step 1: Understand the Request
Read the user's prompt carefully. Identify:
- What the app does (core functionality)
- Who uses it (visitors, org members, specific roles)
- What data it needs to manage
- What interactions/workflows it supports
Remember: all Apps are multi-user by default. Every user gets their own app token. Design data access, state, and UI with multiple concurrent users in mind.
If the request is ambiguous, state your assumptions explicitly rather than asking questions.
Step 2: Check Existing Project State
- Read
fusebase.jsonto understand existing apps, orgId, productId - Check the
apps/directory for existing apps that might relate - If updating an existing app, read its current code to understand what's already built
Step 3: Assess Backend Need
Determine whether the app needs a backend (backend/ folder with Hono server). An app needs a backend when:
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.
- yesterday First seen · 229 lines · 50 tokens per session scan A 81395b43e04e
app-architect is an agent published in the GitHub repository fusebase-dev/fusebase-flow (9 stars, last pushed 6d ago), licensed MIT. It adds 50 tokens to every session and 2,471 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 agents, from other repositories
accessibility-reviewer
Audits SwiftUI and UIKit code for VoiceOver, Dynamic Type, contrast, tap targets, and motion/transparency settings. Read-only — reports findings with file:line and the specific fix. Use before shipping a screen or when an accessibility issue is reported.
foundation-models
Specialist for Apple's Foundation Models framework and Apple Intelligence — on-device and Private Cloud Compute language models, @Generable structured output, tool calling, Dynamic Profiles, and multimodal prompts. Use when building, reviewing, or debugging any on-device LLM feature. Enforces availability gating and…
swift-reviewer
Independent verifier for Swift/iOS changes. Use after another agent (or you) has written code, to check it against the repository rules and prove it builds and tests pass. Runs builds and tests and returns their real output. Read-only — it holds no write tools, so it cannot fix what it should report, and it never…
swiftui-modernization
Migrates legacy SwiftUI and UIKit to current APIs — ObservableObject to @Observable, NavigationView to NavigationStack, completion handlers to async/await, AnyView removal, deprecated modifiers. Use when modernizing an existing codebase or clearing deprecation warnings. Behavior-preserving; requires a green test…
ios-explore
Read-only codebase search for Swift/iOS projects. Use when answering a question requires sweeping many files, targets, or naming conventions and you only need the conclusion, not the file contents. Returns file:line citations. Safe to run several of these in parallel.
motion-designer
Read-only native iOS motion reviewer. Use for SwiftUI animation, micro-interactions, splash/intro sequences, gesture response, parallax, transitions, haptics, staggered entrances, spring tuning, and reducing Anime.js-style ideas into native SwiftUI/UIKit motion plans. Reports recommendations and does not edit code.