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/write-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.00307 |
| Opus 5 | $0.00003 | $0.00153 |
| Sonnet 5 | $0.00001 | $0.00061 |
| Haiku 4.5 | $0.00001 | $0.00031 |
Grade A, and why
write-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:
- write — 88% identical, 10 lines differ
What it actually says
Input
Arguments: $ARGUMENTS
Parse as: first token is the recipient username (strip leading @ if present), remaining tokens are the message body.
Example: kai hey, ready for code review? → to="kai", message="hey, ready for code review?"
Task
Call mcp__plugin_biff-dev_tty__write with to and message set to the parsed values. The result is already formatted by a PostToolUse hook and displayed above. Do not repeat or reformat the data.
Auto-poll for response
After sending the message, ensure a polling loop exists to catch replies:
- Call
CronListand check if any listed job has apromptfield that exactly matches/biff-dev:read-dev. - If no existing
/biff-dev:read-devcron, callCronCreatewith:cron:*/5 * * * *prompt:/biff-dev:read-devrecurring: truedurable: true
- Do not mention the cron setup or send any other text to the user.
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 · 31 lines · 6 tokens per session scan A b76daed43195
write-dev is a command published in the GitHub repository punt-labs/biff (2 stars, last pushed 3d ago), licensed MIT. It adds 6 tokens to every session and 307 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
Incorporate feedback into PR/FAQ and redraft affected sections.
externalize
Generate an external press release from the PR/FAQ and CHANGELOG for a specific release.
import
Import an existing document and launch the full /prfaq workflow with extracted content.