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/biff/read-devgit clone --depth 1 https://github.com/punt-labs/biffWhat 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.00006 | $0.00252 |
| Opus 5 | $0.00003 | $0.00126 |
| Sonnet 5 | $0.00001 | $0.00050 |
| Haiku 4.5 | $0.00001 | $0.00025 |
Grade A, and why
read-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 2d 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:
- read — 89% identical, 4 lines differ
What it actually says
Call mcp__plugin_biff-dev_tty__read_messages with no arguments. The tool retries a transport error once internally, per inbox, and never raises for a transport failure — every outcome below is a normal return value to check, never an error to catch.
If the result says "No new messages.", do not emit any text — this is a confirmed-empty result.
If the result starts with "Could not check ", surface it plainly and do not treat it as, or report it like, an empty inbox. This can appear standalone (every inbox failed) or as a leading line before rendered messages (some inboxes succeeded and are shown below it, one specific inbox could not be checked) — in the combined case, do not drop the warning line to make the output look clean; both facts are real.
Otherwise, emit the tool output exactly as returned — character for character, including the leading ▶ unicode character. Do not reformat, add commentary, wrap in code fences, convert to markdown tables, or add boxes around the output.
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.
- 2d ago First seen · 14 lines · 6 tokens per session scan A 7d285e215a7b
read-dev is a command published in the GitHub repository punt-labs/biff (2 stars, last pushed 2d ago), licensed MIT. It adds 6 tokens to every session and 252 once invoked, about $0.0000 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-31.
Other commands, from other repositories
meeting-listen
Play back a completed meeting summary as a voiced debate between personas.
meeting-hive
Run an autonomous PR/FAQ review meeting where four personas debate and reach consensus without user intervention.
vote
Assess whether a PR/FAQ should move forward with a structured go/no-go decision.
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.
meeting
Run a simulated PR/FAQ review meeting with agentic personas.