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/invite-with-passwordnpx skills add fusebase-dev/fusebase-flow --skill invite-with-passwordgit 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.00106 | $0.01279 |
| Opus 5 | $0.00053 | $0.00639 |
| Sonnet 5 | $0.00021 | $0.00256 |
| Haiku 4.5 | $0.00011 | $0.00128 |
Grade A, and why
invite-with-password 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 — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Invite With Password
When to use this
The app owns its account UI: a custom login form, a custom onboarding screen, its own password setup and reset — the user never leaves the app and never sees a Fusebase auth page. Typical asks: "invite my clients into the portal app", "our own branded sign-in", "let them pick a password when they accept the invite".
Without this, an invited user has no password they know, so the only way in is the platform's
"Trying to reset your password?" email — nonsense for somebody who never registered, and it drops
them onto a platform page in the middle of your onboarding. setFusebaseInitialPassword is what
makes an app-owned form possible: the invitee sets their first password inside the app.
The reset half of app-owned auth is a different op: requestFusebaseRestoreKey mints a restore
key without sending the platform email, so the app can send its own branded reset mail — see
fusebase-gate/references/fusebase-auth.md § Password Restore. This skill covers the first
password only.
Flow
Invite → invitee opens the app through the magic link → app shows a Create your password form → the account signs in with email + password from then on. No platform email beyond the invite itself.
Both pre-provisioning paths — addOrgUser (orgRole: 'client', autoConfirmClientInvite: true) and
createAppMagicLink (addToAccessPrincipals: true) — create an account holding a random password the
user never learns, which is why the invitee needs setFusebaseInitialPassword to get one they know.
- Invite — app backend,
process.env.FBS_FEATURE_TOKEN:addOrgUserorcreateAppMagicLink. - Open — invitee clicks the link, the platform activates it, the app host gets the invitee's
fbsfeaturetoken. Do the mandatory magic-link exchange first (fusebase-gate/references/fusebase-auth.md). - Detect — SPA reads
needsInitialPasswordfrom/auth/context.true= this account has never had a password → render the password form. Absent/false→ do not offer it. - Set — app backend forwards the invitee's own token to Gate.
FBS_FEATURE_TOKENgets403. - Sign in right away — a
200mints no session and drops every existing session of the account, including the magic-link one, so log the user back in with the password from the same form.
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 · 82 lines · 106 tokens per session scan A d8c5de17dea0
invite-with-password is a skill published in the GitHub repository fusebase-dev/fusebase-flow (9 stars, last pushed 7d ago), licensed MIT. It adds 106 tokens to every session and 1,279 once invoked, about $0.0005 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.