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.
git 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/rules/fusebase-dev/fusebase-flow/fusebase-flow-validation)<a href="https://agentmods.dev/rules/fusebase-dev/fusebase-flow/fusebase-flow-validation"><img src="https://agentmods.dev/badge/rules/fusebase-dev/fusebase-flow/fusebase-flow-validation.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.1 | $0.00000 | $0.00432 |
| Opus 5 | $0.00000 | $0.00216 |
| Sonnet 5 | $0.00000 | $0.00086 |
| Haiku 4.5 | $0.00000 | $0.00043 |
Grade A, and why
fusebase-flow-validation 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 today.
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.
What it actually says
Fusebase Flow — validation rules
Gate report (AI Developer-side)
Required fields are canonical in policies/gate-contracts.yml: gate_report (machine schema); the producer template is templates/gate-report.md. Do not restate the field list.
If any field is missing, redirect: "Gate report missing . Per FR-05, complete reports only. Re-run."
Reproducibility before fix (FR-10)
When operator describes a single observed failure ("the system did X"):
- Don't draft a fix immediately.
- Reproduce 3 times under the same conditions.
- Outcomes:
- 3/3 reproduce → systemic; draft fix
- 1/3 or 2/3 → likely model variance / non-determinism; document and recommend no-op close
- 0/3 → close as no-op-needed
Smoke prompts (post-deploy)
When verification-gate.md defines numbered S1..Sn:
- Follow
flow-skills/smoke-testing/SKILL.md - Verify the operator-visible outcome, not only supporting checks
- Inspect the ground-truth diagnostic surface named by S
- Persist evidence to
docs/tmp/handoff/<date>-<slug>-smoke/ - Compute pass ratio against gate contract threshold
- If below threshold or end-to-end smoke is not feasible, do NOT mark spec DONE; surface failure or
PENDING-OPERATOR-SMOKEwith concreteS<n> observed Y, expected Z/ missing prerequisite
What this rule does NOT do
- Approve deploy (that's
release-deploy-reporting) - Auto-fix lint/typecheck errors
- Skip reproducibility-before-fix
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.
- today First seen · 42 lines · 0 tokens per session scan A 089dfb282abd
fusebase-flow-validation is a cursor rule published in the GitHub repository fusebase-dev/fusebase-flow (9 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 432 tokens. 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-09-08.
Other cursor rules, from other repositories
playwright-defect-tracking-cursorrules-prompt-file
Cursor rules for Playwright development with defect tracking.
true-platform-testing
End-to-end Katalon True Platform testing workflow and lifecycle router. Use when one request spans several stages and no single skill owns all of it, for example analyze a requirement, design and import the cases, build a suite, run it with AI, and report the outcome. Also use to route any testing request across the…
test-case-to-katalon-studio
Convert Katalon True Platform/TestOps manual test cases into Katalon Studio automation inside a local Studio Test Project checkout. Use when you need to author or extend a .tc test case file and its paired Groovy script under Scripts/, keep test case variable GUIDs consistent with the .ts test suite bindings that read…
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…
analyze-failures
Triage Katalon True Platform/TestOps test failures and file defects. Use when you need to investigate failed test results, classify each failure as product defect vs automation defect vs environment/data issue, cluster failures by common signature, find likely root cause from execution data, and optionally create…