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/business-logic-guardiannpx skills add fusebase-dev/fusebase-flow --skill business-logic-guardiangit clone --depth 1 https://github.com/fusebase-dev/fusebase-flowWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/fusebase-dev/fusebase-flow/business-logic-guardian)<a href="https://agentmods.dev/skills/fusebase-dev/fusebase-flow/business-logic-guardian"><img src="https://agentmods.dev/badge/skills/fusebase-dev/fusebase-flow/business-logic-guardian.svg" alt="Measured on agentmods" height="20"></a>What 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.00137 | $0.01617 |
| Opus 5 | $0.00068 | $0.00809 |
| Sonnet 5 | $0.00027 | $0.00323 |
| Haiku 4.5 | $0.00014 | $0.00162 |
Grade A, and why
business-logic-guardian 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 5d 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 — 118 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Business Logic Guardian
Style: Mode-B-lite. Artifact-gated — inert unless a business-logic doc exists at ANY path in § Doc-path resolution.
Purpose
Protect documented business logic during fixes and improvements. The business-logic doc is a fast navigation/verify layer: confirm a change does not silently break documented behavior before committing. Complements FR-20 (zoom-out) and FR-10 (reproduce-before-fix).
Consumes whichever business-logic doc exists. Per FR-23 (
flow-skills/documentation-budget/SKILL.md), the AI-default authoring format is the retrieval indextemplates/business-logic-index.md(tables + source paths); the narrativetemplates/business-logic.mdis the explicit human-readable option. This skill reads either as the guard layer.
Doc-path resolution (the gate checks ALL of these)
| Doc | Path | Role |
|---|---|---|
| Retrieval index (AI-default, FR-23) | docs/<app>/business-logic-index.md |
primary guard layer when present |
| Flow narrative (human option) | docs/<app>/business-logic.md |
guard layer; supplementary if index exists |
CLI-edition narrative (app-business-docs canonical) |
docs/en/business-logic.md |
guard layer for Fusebase CLI teams using the provider skill |
If several exist: index first, narratives supplementary. The gate no-ops only when none of the three exists.
When to invoke
- Any doc in § Doc-path resolution exists —
docs/<app>/business-logic-index.md(AI-default),docs/<app>/business-logic.md, ordocs/en/business-logic.md(app-business-docscanonical) — AND a fix/improvement touches business behavior. If several exist, the index is the primary guard layer; narratives are supplementary. - Operator says "don't break the business logic", "does this change behavior".
- During Implement / post-gate fixes on an app that has documented logic.
Do not invoke when
- None of the § Doc-path resolution paths exists (
docs/<app>/business-logic-index.md,docs/<app>/business-logic.md,docs/en/business-logic.md) → silent no-op; do not create any of them (author deliberately viaapp-business-docs— which writesdocs/en/business-logic.md— or the FR-23business-logic-indextemplate). - Net-new feature with no documented logic yet.
- Pure cosmetic edits.
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.
- 5d ago First seen · 118 lines · 137 tokens per session scan A 1da34d3d70ca
business-logic-guardian is a skill published in the GitHub repository fusebase-dev/fusebase-flow (9 stars, last pushed 10d ago), licensed MIT. It adds 137 tokens to every session and 1,617 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.