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/communicationnpx skills add fusebase-dev/fusebase-flow --skill communicationgit 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.00054 | $0.01663 |
| Opus 5 | $0.00027 | $0.00831 |
| Sonnet 5 | $0.00011 | $0.00333 |
| Haiku 4.5 | $0.00005 | $0.00166 |
Grade A, and why
communication 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 — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Do not re-Read this file if it is already in your context. If this exact SKILL.md body is already present in your context (surfaces that auto-load
.claude/skills/or.agents/skills/), do not Read this file again — seeing the name/description in a skill index does not count. If it is not present, read it once. Delegated sub-agent sessions do not inherit an auto-load: they read it.Surface truth (AC11, verified): no surface injects this body. Claude Code (
.claude/skills/) and Codex (.agents/skills/, optionalskills_dir) supply the description/metadata only; Gemini, Copilot, Cursor and delegated sub-agents supply nothing. Read it once when the body is not already in your context.
Communication
Mode A — operator chat (FR-08). Visual, concrete, brief: ASCII when state is spatial, tight status otherwise. Operators scan; they don't read. Mode B — internal artifacts (FR-09). What a later AI session loads: dense, tabular, front-loaded, concrete identifiers; no narrative padding or preamble. Both apply in every session — no exemption, never downgraded to on-demand.
Prohibition — visuals never in Mode-B files. ASCII goes in chat only, never in any file on the Mode-B list below: visuals cost tokens on every load and freeze transient state. references/patterns.md is the library — not a licence to embed visuals elsewhere.
File classification
Mode B applies (AI-optimized; no prose padding, no visuals):
docs/specs/<slug>/{spec,decisions,tasks,verification-gate,research,data-model,clarify-conversation}.md
docs/backlog/<slug>/README.md · docs/backlog/index.md
docs/tmp/handoff.md (active continuity; superseded each session — FR-18 / FR-23 Tier 2)
docs/tmp/handoff/<date>-<slug>-{implement,deploy,architect}.md (formal relays)
docs/problem-catalog/{<slug>/problem.md,README.md} · docs/skills/{<slug>/SKILL.md,README.md}
Mode B-lite (this file's tier): flow-skills/*/SKILL.md · workflows/*.md · docs/{compatibility,hook-coverage,rail-mapping}.md · audit/README.md
What ships with it
2 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.
- yesterday First seen · 95 lines · 54 tokens per session scan A 91f95da9e5b2
communication is a skill published in the GitHub repository fusebase-dev/fusebase-flow (9 stars, last pushed 7d ago), licensed MIT. It adds 54 tokens to every session and 1,663 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 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.