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 instructions/fizzbee-io/fizzbee/fizzbee-mbtgit clone --depth 1 https://github.com/fizzbee-io/fizzbeeWrote 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/fizzbee-io/fizzbee/fizzbee-mbt)<a href="https://agentmods.dev/instructions/fizzbee-io/fizzbee/fizzbee-mbt"><img src="https://agentmods.dev/badge/instructions/fizzbee-io/fizzbee/fizzbee-mbt.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.03381 | $0.03381 |
| Opus 5 | $0.01690 | $0.01690 |
| Sonnet 5 | $0.00676 | $0.00676 |
| Haiku 4.5 | $0.00338 | $0.00338 |
Grade A, and why
fizzbee fizzbee-mbt.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 4d 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 — 410 lines — stays where its author put it; the contents beside it link to each section on GitHub.
FizzBee Model-Based Testing (MBT)
FizzBee MBT generates exhaustive test sequences from a verified Fizz spec and runs them against the real system under test (SUT). Supported languages: TypeScript, Go, Rust, Java.
Examples repository: https://github.com/fizzbee-io/fizzbee-mbt-examples
Installation
brew tap fizzbee-io/fizzbee && brew install fizzbee
brew tap fizzbee-io/fizzbee-mbt && brew install fizzbee-mbt
Workflow
- Write and verify a
.fizzspec:fizz spec.fizz→ PASSED - Scaffold adapter code:
fizz mbt-scaffold --lang <lang> --gen-adapter --out-dir <dir> spec.fizz - Implement adapter methods in the generated
*_adaptersfile - Start MBT server:
fizzbee-mbt-server --states_file <spec>/out/run_<timestamp>/ - Run tests
Scaffold Commands
fizz mbt-scaffold --lang typescript --gen-adapter --out-dir src/fizztests/ spec.fizz
fizz mbt-scaffold --lang go --go-package myapp --gen-adapter --out-dir fizztests/ spec.fizz
fizz mbt-scaffold --lang rust --gen-adapter --out-dir src/fizztests/ spec.fizz
fizz mbt-scaffold --lang java --java-package org.example.myapp --gen-adapter --out-dir fizztests/ spec.fizz
Generated files per spec (do not edit interfaces or test files — only implement the adapters):
| File | Edit? |
|---|---|
*_interfaces.* — role + model interfaces |
No |
*_adapters.* — stub methods to implement |
Yes |
*_test.* — test runner wiring |
No |
Language Feature Support
| Feature | TypeScript | Go | Rust | Java |
|---|---|---|---|---|
| Sequential testing | ✓ | ✓ | ✓ | ✓ |
| Concurrent testing | ✓ (cooperative) | ✓ | ✓ | ✓ |
| StateGetter | ✓ | ✓ | ✓ | ✓ |
| SnapshotStateGetter | ✓ | ✓ | ✓ | ✓ |
| Sentinel values | ✓ IGNORE/ignored() |
✓ | ✓ | ✓ |
| AfterActionHook | ✓ | — | — | — |
| OverridesProvider (fuzzing) | ✓ | — | — | — |
| Playwright utilities | ✓ | — | — | — |
TypeScript / Playwright (Primary UI/E2E Target)
Package
npm install @fizzbee/mbt
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.
- 4d ago First seen · 410 lines · 3,381 tokens per session scan A f6e4cd5d5359
fizzbee fizzbee-mbt.instructions.md is an instructions file published in the GitHub repository fizzbee-io/fizzbee (347 stars, last pushed 9d ago), licensed Apache-2.0. It adds 3,381 tokens to every session, about $0.0169 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-30.
Other instructions, from other repositories
vera AGENTS.md
AGENTS.md instructions for aallan/vera, covering agents.md — instructions for ai agents, for agents writing vera code, conformance programs as reference, workflow and commands.
emilia-protocol CLAUDE.md
Claude Code instructions for emiliaprotocol/emilia-protocol, covering emilia protocol - repo guide, required context, critical, build & ship and outbound & claims.
emilia-protocol copilot-instructions.md
Copilot instructions for emiliaprotocol/emilia-protocol: Read AGENTS.md and AICONTEXT.md before proposing changes. Current evidence and provenance are in public/.well-known/emilia-context.json. Treat archived, staged, private, and outreach documents as non-authoritative for current behavior or standards status.
emilia-protocol GEMINI.md
Gemini CLI instructions for emiliaprotocol/emilia-protocol: Read AGENTS.md and AICONTEXT.md before analyzing or editing this repository. Use public/.well-known/emilia-context.json for current evidence counts and provenance. Do not infer current behavior or standards status from archived, staged, private, or randomly…
jacobian AGENTS.md
AGENTS.md instructions for morluto/jacobian, covering jacobian agent guide, what we are building, non-negotiable boundaries, implement mathematics directly and mathematical boundedness is a proof obligation.
aristo CLAUDE.md
Instructions for aretta-ai/aristo, covering claude.md — aristo working agreement, §1. commit size — small or medium only, §2. commit messages — semantic / conventional, §3. changelog.md — one line per commit, in the same commit and §4. test-first — no test, no claim of correctness.