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/punt-labs/biffWrote 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/biff/wall-dev)<a href="https://agentmods.dev/commands/punt-labs/biff/wall-dev"><img src="https://agentmods.dev/badge/commands/punt-labs/biff/wall-dev/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/commands/punt-labs/biff/wall-dev"><img src="https://agentmods.dev/badge/commands/punt-labs/biff/wall-dev.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.00006 | $0.00302 |
| Opus 5.5 | $0.00002 | $0.00121 |
| Sonnet 5.5 | $0.00001 | $0.00060 |
| Haiku 4.5 | $0.00001 | $0.00030 |
Grade A, and why
wall-dev 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 1mo 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- wall — 88% identical, 4 lines differ
What it actually says
Input
Arguments: $ARGUMENTS
Parse as one of three modes:
- Clear: if arguments are exactly
clear→ call withclear=True - Post with duration: if the last token matches a duration pattern (
30m,2h,1d,3d), it is the duration and everything before it is the message →message="...", duration="2h" - Post with default: otherwise the entire argument string is the message →
message="..."
If no arguments are provided, call with no parameters (shows current wall).
Examples:
release freeze — do not push to main→message="release freeze — do not push to main"deploy window open 2h→message="deploy window open",duration="2h"clear→clear=true- (empty) → no parameters
Task
Call mcp__plugin_biff-dev_tty__wall with the parsed values. The result is already formatted by a PostToolUse hook and displayed above. Do not repeat or reformat the data. Do not send any text after the tool call.
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.
- 1mo ago First seen · 30 lines · 6 tokens per session scan A 15c48a848fa9
wall-dev is a command published in the GitHub repository punt-labs/biff (2 stars, last pushed yesterday), licensed MIT. It adds 6 tokens to every session and 302 once invoked, about $0.0000 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-08-31.
Other commands, from other repositories
feedback-to-us
Tell us how the prfaq plugin is working for you (anonymous 1-5 feedback).
setup
Install and configure fuzz, probcli, and lean dependencies.
badge
Generate a stage-colored badge and embed it in your README.
contracts-dev
Generate runtime contracts (preconditions, postconditions, invariants) from a Z specification.
code2model-dev
Create a Z specification for stateful entities in a system.
partition-dev
Derive test cases from Z specification using TTF testing tactics.