Borrowing it
Nothing to install: this file belongs to fusebase-dev/fusebase-flow. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/fusebase-dev/fusebase-flow/main/.github/instructions/validation.instructions.mdgit 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/instructions/fusebase-dev/fusebase-flow/validation)<a href="https://agentmods.dev/instructions/fusebase-dev/fusebase-flow/validation"><img src="https://agentmods.dev/badge/instructions/fusebase-dev/fusebase-flow/validation/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/instructions/fusebase-dev/fusebase-flow/validation"><img src="https://agentmods.dev/badge/instructions/fusebase-dev/fusebase-flow/validation.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.00516 | $0.00516 |
| Opus 5.5 | $0.00206 | $0.00206 |
| Sonnet 5.5 | $0.00103 | $0.00103 |
| Haiku 4.5 | $0.00052 | $0.00052 |
Grade A, and why
fusebase-flow validation.instructions.md 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 7d 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.
What it actually says
Fusebase Flow — validation & QA instructions for GitHub Copilot / VS Code
Apply when running gate checks, reviewing diffs against the gate contract, or verifying smoke prompts.
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."
Rows are AI Developer PASS/FAIL claims; only the Product Owner side issues the verdict, after its own recount, and gate rounds are bounded (default 2, then BLOCKED-AT-gate-budget) per workflows/verification-gate.md.
Reproducibility before fix (FR-10)
When the operator describes a single observed failure:
- 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 → deterministic app code = real race/state bug unless Explained-external; LLM/agent behavior = model-variance no-op close (
flow-skills/validation-and-qa/SKILL.mdSub-mode C). - 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 the 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 scope does NOT do
- Approve deploy (that's the
release-deploy-reportingskill) - Auto-fix lint / typecheck errors — surface them
- Skip reproducibility-before-fix (FR-10)
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.
- 7d ago Changed · +2 lines · +80 tokens per session b1c63b36db53
- 1mo ago First seen · 42 lines · 436 tokens per session scan A c474cb7b79e0
fusebase-flow validation.instructions.md is an instructions file published in the GitHub repository fusebase-dev/fusebase-flow (9 stars, last pushed today), licensed MIT. It adds 516 tokens to every session, about $0.0021 per session on Opus 5.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-09-08.
Other instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.