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-e2e-testsnpx skills add fusebase-dev/fusebase-flow --skill app-e2e-testsgit 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.00088 | $0.01503 |
| Opus 5 | $0.00044 | $0.00751 |
| Sonnet 5 | $0.00018 | $0.00301 |
| Haiku 4.5 | $0.00009 | $0.00150 |
Grade A, and why
app-e2e-tests 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 — 121 lines — stays where its author put it; the contents beside it link to each section on GitHub.
App E2E tests (environment-aware)
One suite in tests/e2e/, same specs against every environment of the
project. Environments (fusebase env) supply everything varying between
stages: base URLs, org/app ids, test users.
When e2e is being added as part of an environment migration, first follow the local guide App Environment Migration Guide, then use this skill for the Playwright harness and CI details.
When adding e2e to an existing project, first follow the local guide E2E Playwright Setup Guide: audit environments, prefer non-prod targets, warn before any prod run, scaffold from the CLI template, and wire GitLab CI.
Scaffold
fusebase scaffold --template e2e --dir tests/e2e
cd tests/e2e && npx playwright install chromium
FUSEBASE_ENV=<env> npm test
Layout — one project per app
playwright.config.ts generates one Playwright project per app in
fusebase.json (name = the app's key, falling back to subdomain), each
pinned to that app's env-effective URL. Specs live in:
specs/common/**— universal specs, run for EVERY app, app-aware viatest.info().project.name.specs/<appKey>/**— that app's own specs.
Adding an app: give it a short key in fusebase.json (e.g. probe),
mkdir specs/<key>, add specs, add the key to the CI matrix APP list. Run a
single app with --project=<appKey>.
Cross-app / portal flows (registration → access propagation across apps +
portal) span more than one app and have NO single baseURL — they do not
belong to any app's project. Put them in specs/integration/; the config
adds an integration project whose specs build each app's URL via
appBaseUrl(env, key). Add integration to the CI matrix APP list.
Recipes: examples/cross-app-access.spec.ts, examples/portal-access.spec.ts.
(Product-scoped magic links + one org = shared session across app subdomains,
which is exactly what these flows assert.)
Non-negotiables
- Stage guard stays.
specs/common/stage.spec.tsasserts each app's deployedfusebase-env.jsonmatches the target env AND app. Never delete it — a run against the wrong stage/app is worse than no run. - No hardcoded env data. Hosts, org/app ids, credentials come only from
helpers/env.ts(environments/<name>.json+.env.<name>) and the project'sbaseURL. A spec that embeds a URL or id silently breaks on another environment or app. - Fixtures self-skip. Use the
fixtureUser(env, key)+test.skippattern (seeexamples/role-matrix.spec.ts) so specs stay runnable while fixtures roll out per env. - Cleanup. Tests that create data must delete it — prod-test environments are real orgs.
- No secrets in git. Passwords via
PW_USER_<KEY>_PASSWORDin.env.<name>locally / CI variables in pipelines. Reports and traces are gitignored.
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 · 121 lines · 88 tokens per session scan A 01255cc713d7
app-e2e-tests is a skill published in the GitHub repository fusebase-dev/fusebase-flow (9 stars, last pushed 7d ago), licensed MIT. It adds 88 tokens to every session and 1,503 once invoked, about $0.0004 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
lov-app-generator
Use when the user asks for "App生成器", "生成 Web App", "生成 Tauri App", "生成原生 macOS App", "Finder Quick Action", "只创建 web", or to standardize an existing app with branding, CI/CD, native integration, and Lovinsp where applicable.
lov-integrate-lovinsp
幂等集成 lovinsp (click-to-code) 到当前前端项目，并支持从 code-inspector 自动迁移。 Use when the user asks to "装 lovinsp"、"集成 lovinsp"、"接入点击跳转源码"、"click to code"、 "从 code-inspector 迁移"，or when scaffolding/upgrading a browser-rendered app that needs click-to-source support. Also trigger when another skill (例如 lov-app-generator) requires…
chrome-devtools
Use Chrome DevTools MCP to control and inspect a live Chrome instance for network, console, performance, rendering, and Deep debugging. Pairs with playwright-cli (deterministic interaction/E2E) — complements, not duplicates.
upload-report
Run automation and upload or verify Katalon Platform reports for Katalon Studio/KRE, JUnit XML, and Playwright reports. Use when you need to combine Katalon MCP project/result discovery with Katalon CLI execution, Katalon Report Uploader, or @katalon/playwright-reporter; configure report folders, report types…
playwright-execute
Run Playwright tests or suites and upload the resulting report to Katalon True Platform. Use when you need to execute Playwright scripts, package scripts, spec files, projects, or suites, configure or verify @katalon/playwright-reporter, upload Playwright reports with Katalon CLI/reporter commands, and verify uploaded…
test-case-to-playwright
Convert Katalon True Platform/TestOps manual test cases, test suites, or requirement-linked cases into Playwright TypeScript automation. Use when you need to fetch/read Katalon Platform test cases and implement Playwright scripts, create or adapt a Playwright framework, apply Page Object Model and fixtures, or…