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 commands/punt-labs/z-spec/b-checkgit clone --depth 1 https://github.com/punt-labs/z-specWrote 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/commands/punt-labs/z-spec/b-check)<a href="https://agentmods.dev/commands/punt-labs/z-spec/b-check"><img src="https://agentmods.dev/badge/commands/punt-labs/z-spec/b-check.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.00008 | $0.00602 |
| Opus 5 | $0.00004 | $0.00301 |
| Sonnet 5 | $0.00002 | $0.00120 |
| Haiku 4.5 | $0.00001 | $0.00060 |
Grade A, and why
b-check 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 6d 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.
This is a copy
95% identical to b-check-dev — 2 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Check B Machine with probcli
Type-check a B machine (.mch, .ref, or .imp) using probcli.
Input
File: $ARGUMENTS
Process
0. Check Prerequisites
Verify probcli is installed:
PROBCLI="${PROBCLI:-$HOME/Applications/ProB/probcli}"
if ! which probcli >/dev/null 2>&1 && [ ! -x "$PROBCLI" ]; then
echo "PROBCLI_NOT_FOUND"
fi
If probcli not found: Stop and tell the user:
probcli is not installed. Run
/z-spec:setup probclifirst.
1. Locate the Machine
If a file path is provided, use it directly.
If no file specified:
- Look in
specs/for.mch,.ref, or.impfiles - Present options if multiple files exist
2. Run probcli Type-Check
probcli <file>
probcli parses the machine, checks types, and reports errors. Unlike Z specifications (which use fuzz for type-checking), B machines use probcli for both type-checking and animation.
3. Interpret Results
Success: probcli exits with code 0, no error output.
Errors: probcli reports syntax errors, type errors, and well-formedness violations.
Common errors and fixes:
| Error | Likely Cause | Fix |
|---|---|---|
Syntax Error |
Invalid B syntax | Check clause order (SETS before VARIABLES before INVARIANT) |
Type Error |
Mismatched types in predicate | Verify variable types in INVARIANT match OPERATIONS usage |
Identifier not found |
Undefined variable or constant | Add to VARIABLES or CONSTANTS clause |
Parse error: expecting END |
Missing END keyword | Each PRE/IF/SELECT needs a matching END |
Not a B file |
Wrong file extension | Use .mch, .ref, or .imp |
PROPERTIES missing |
CONSTANTS without PROPERTIES | Add PROPERTIES clause with typing constraints |
4. Report Results
If successful:
- Confirm the machine type-checks
- List the machine's SETS, VARIABLES, and OPERATIONS
If errors:
- List each error with location
- Suggest specific fixes
- Offer to apply fixes
Reference
- B notation:
reference/b-notation.md - B machine patterns:
reference/b-machine-patterns.md - probcli options:
reference/probcli-guide.md
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.
- 6d ago First seen · 84 lines · 8 tokens per session scan A a01b0f8ea12e
b-check is a command published in the GitHub repository punt-labs/z-spec (5 stars, last pushed 2d ago), licensed MIT. It adds 8 tokens to every session and 602 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it A with 0 findings. It is 95% identical to b-check-dev, differing in 2 lines, and is treated as a copy.
Other commands, from other repositories
feedback-to-us
Tell us how the prfaq plugin is working for you (anonymous 1-5 feedback).
badge
Generate a stage-colored badge and embed it in your README.
import
Import an existing document and launch the full /prfaq workflow with extracted content.
research
Research evidence for PR/FAQ claims and generate biblatex citations.
review
Peer review a PR/FAQ document for quality and decision readiness.
streamline
Tighten a PR/FAQ by removing redundancy, weasel words, and bloat.