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-specs)<a href="https://agentmods.dev/rules/fusebase-dev/fusebase-flow/fusebase-flow-specs"><img src="https://agentmods.dev/badge/rules/fusebase-dev/fusebase-flow/fusebase-flow-specs/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/rules/fusebase-dev/fusebase-flow/fusebase-flow-specs"><img src="https://agentmods.dev/badge/rules/fusebase-dev/fusebase-flow/fusebase-flow-specs.svg" alt="Reviewed on agentmods" width="80" 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.00540 |
| Opus 5 | $0.00000 | $0.00270 |
| Sonnet 5 | $0.00000 | $0.00108 |
| Haiku 4.5 | $0.00000 | $0.00054 |
Grade A, and why
fusebase-flow-specs 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 — Mode B (full) for spec-side artifacts
Files in this glob are read by AI sessions, not human readers. Optimize for AI context efficiency.
Mode B principles (full)
- Front-load the answer — first sentence/cell IS the answer; reasoning second.
- Tables over prose for structured data (3+ comparable rows → table).
- Bullets over paragraphs for enumerables (3+ items → bullets).
- Concrete over abstract —
T17,sha:abc1234,repository.ts:42-58— never "the earlier change". - Predictable section names — use
templates/headers verbatim. - No narrative storytelling — "Decision: X. Reason: Y. Alternatives: Z (rejected: A)." not "I considered X then thought about Y..."
- Cross-references precise —
spec.md:42-58not "see above". - No restatement of context already in adjacent loaded files.
- Status fields tag-style —
Status: DONE,Lock status: LOCKED. - No hedging unless filing as a clarify item.
- Consistent vocabulary — use FLOW_RULES.md / AGENTS.md project-specific terms verbatim.
- No human-onboarding preamble — open with payload.
Substrates
docs/specs/<slug>/spec.md←templates/spec.mddocs/specs/<slug>/decisions.md←templates/decisions.mddocs/specs/<slug>/tasks.md←templates/tasks.mddocs/specs/<slug>/verification-gate.md←templates/verification-gate.mddocs/tmp/handoff/<YYYY-MM-DD>-<slug>-<stage>.md← workflow templates inworkflows/docs/problem-catalog/<slug>/problem.md←templates/problem-catalog-entry.md
Anti-patterns
- ASCII visuals in spec.md/decisions.md/tasks.md (visuals belong in chat per FR-08)
- Restating constitution / spec content inside decisions.md
- Free-form decision write-ups instead of letter-prefixed matrix
- Long preambles ("This document captures...")
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 · 41 lines · 0 tokens per session scan A 50dbac8c3ec6
fusebase-flow-specs 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 540 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
vibeflow
Vibeflow spec-driven development methodology — guardrails, pipeline, and project knowledge system.
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…
test-maintenance
Maintain and evolve a Katalon True Platform/TestOps regression suite as the application changes. Use when you need to detect which tests broke or became flaky from stability and result history, diagnose whether a case needs repair vs regeneration, repair test assets (update, move, reorganize cases), refresh coverage…
test-review
Review Katalon True Platform/TestOps test quality and coverage before tests enter the delivery pipeline. Use when you need to check whether a suite is ready to run, review requirement and configuration coverage, assess test-case quality and flakiness/stability, spot weak or unreliable cases, and produce a review…
client-workflow-bootstrap
Cursor rule "client-workflow-bootstrap" from ulises-jeremias/agent-toolkit, covering agent vs skill rule — why agent (cite clause), when to use vs holistic, caller / skills / handoff, interview process and gate before generating.
coding-style
Supercharge your Cursor/AI IDE with rules, commands, and skills.