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/product-docs-firstnpx skills add fusebase-dev/fusebase-flow --skill product-docs-firstgit 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.00913 |
| Opus 5 | $0.00044 | $0.00456 |
| Sonnet 5 | $0.00018 | $0.00183 |
| Haiku 4.5 | $0.00009 | $0.00091 |
Grade A, and why
product-docs-first 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 — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Product Docs First
Style: Mode-B-lite. Artifact-gated — acts only when
docs/<app>/product.mdexists or the operator asks to create one.
Purpose
Design product documentation per app before writing code, so planning and implementation build from a clear product intent instead of guessing. Ingests operator research and the North Star (if present).
When to invoke
- Operator starts a new app and says "design the product docs first", "write product documentation", "what should this app do".
docs/<app>/product.mdalready exists (read it to ground planning).- Operator dropped research in
docs/<app>/research/and asks to turn it into product docs.
Do not invoke when
- No
docs/<app>/product.mdAND the operator did not ask to create one → silent no-op; do not auto-create. - Mid-implementation edits (planning already done).
- Small bug fixes, refactors, copy-only changes, narrow technical tickets, or already-scoped implementation work with no long-lived product-intent change → do not expand product docs (FR-23 /
flow-skills/documentation-budget/SKILL.md).
Required inputs
| Input | Where it lives | If missing |
|---|---|---|
| Product intent (operator answers) | chat | ask in chat (FR-19); do not invent |
| Research (optional) | docs/<app>/research/ |
proceed without; note it |
| North Star (optional) | docs/north-star.md |
proceed; align if present |
| Template | templates/product.md |
stop; template missing |
Procedure
- Gate. If no
docs/<app>/product.mdand no operator request to create one → exit silently. - Ingest any research + the North Star; summarize, cite, never invent domain facts.
- Design the product doc from
templates/product.md: purpose, users, core jobs, key screens/flows, data, the apps this product breaks into (feedsproduct-apps-decomposition), non-goals. - Write
docs/<app>/product.mdwithlast_updatedtoday (only operator-provided content). - Hand to planning (
implementation-planning) grounded in the product doc. - Ambiguity → ask operator (FR-19).
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 · 85 lines · 88 tokens per session scan A ed929e9b9657
product-docs-first 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 913 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
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.