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-quality-patternsnpx skills add fusebase-dev/fusebase-flow --skill app-quality-patternsgit 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.00138 | $0.00954 |
| Opus 5 | $0.00069 | $0.00477 |
| Sonnet 5 | $0.00028 | $0.00191 |
| Haiku 4.5 | $0.00014 | $0.00095 |
Grade A, and why
app-quality-patterns 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 — 61 lines — stays where its author put it; the contents beside it link to each section on GitHub.
App Quality Patterns (QP library)
Style: Mode-B-lite router. The patterns live in
references/<category>.md— load ONLY the categories the feature touches. Each pattern: ID · Trigger · Requirement · Verify (copy-ready smoke recipe) · Anti-pattern.
Purpose
Cross-project behavioral "definition of done" requirements that LLM-built apps repeatedly miss. They are not stack guidance (CLI skills own HOW) and not process rules (FLOW_RULES owns those) — they are WHAT must be true of the built feature. Distilled from recurring consumer-project defects; the library grows one table row at a time.
Category index (load on trigger match)
| Category | File | Load when the feature involves | IDs |
|---|---|---|---|
| State & navigation | references/state-and-navigation.md |
views with filters / search / sort / pagination / tabs / reports / deep links / browser navigation | QP-01..QP-04 |
| Data integrity | references/data-integrity.md |
create / update / delete flows, related records, caching, retries | QP-10..QP-14 |
| UI polish | references/ui-polish.md |
any user-facing UI: lists, forms, dropdowns, dates | QP-20..QP-24 |
Integration contract (how patterns reach the lifecycle)
| Phase | What happens | Owner |
|---|---|---|
| Specify | requirements-specification scans this index; every matching pattern becomes a spec AC citing the QP ID (e.g., "AC4 — filter/report state encoded in URL; refresh restores exact view (QP-01)"). The AC then flows through tasks → gate → smoke → review on the existing machinery — no new gates. |
PO |
| Plan | design brief lists the applicable QP IDs (one line) | PO |
| Implement | the AI Developer reads the cited reference category before building the touching surface | AI Developer |
| Gate/Smoke | the pattern's Verify line is a copy-ready S smoke recipe | PO defines, Deploy executes |
| Review | code-review checks QP-cited ACs were honored (semantic, by reading) |
reviewer |
Growth rule
A defect observed across ≥2 projects (or once with clear generality) → add ONE row to the matching category file (new category file only when none fits) via skill-authoring; ship in the next release. Project-specific patterns go in that project's docs/skills/, never here. Keep rows dense — this library is loaded mid-spec.
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 61 lines · 138 tokens per session scan A ce3cdcd35fb5
app-quality-patterns is a skill published in the GitHub repository fusebase-dev/fusebase-flow (9 stars, last pushed 7d ago), licensed MIT. It adds 138 tokens to every session and 954 once invoked, about $0.0007 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.