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/punt-labs/biff/agents-mdgit 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/instructions/punt-labs/biff/agents-md)<a href="https://agentmods.dev/instructions/punt-labs/biff/agents-md"><img src="https://agentmods.dev/badge/instructions/punt-labs/biff/agents-md.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.00588 | $0.00588 |
| Opus 5 | $0.00294 | $0.00294 |
| Sonnet 5 | $0.00118 | $0.00118 |
| Haiku 4.5 | $0.00059 | $0.00059 |
Grade A, and why
biff AGENTS.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 3d 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
84% identical to dspy-skills AGENTS.md — 35 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 — 68 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Instructions
This project uses bd (beads) for issue tracking. Run bd onboard to get started.
Quick Reference
bd ready --limit=99 # Find available work (show all)
bd show <id> # View issue details
bd update <id> --status in_progress # Claim work
bd close <id> # Complete work
Workflow
This repo delegates non-trivial work through ethos missions, not a
tiered slash-command system — see "Workflow: Ethos Missions and
Pipelines" in CLAUDE.md for mission archetypes (implement, design,
test, review, report, task) and pipeline selection (quick,
standard, full, product, formal, docs, coe, coverage).
Session Close Protocol
Follow the protocol in CLAUDE.md. The short version:
-
File issues for remaining work (
bd create) -
Quality gates must pass (
make check) -
Close beads for finished work (
bd close <id>) -
Push to remote — work is NOT complete until
git pushsucceeds:git pull --rebase git push git status # MUST show "up to date with origin" -
Hand off — provide context for next session
PR workflow (see CLAUDE.md): Do NOT merge a PR immediately. Trigger GitHub Copilot code review, wait for feedback, evaluate and address valid issues, ensure quality gates pass, then merge.
Landing the Plane (Session Completion)
When ending a work session, you MUST complete ALL steps below. Work is NOT complete until git push succeeds.
MANDATORY WORKFLOW:
-
File issues for remaining work - Create issues for anything that needs follow-up
-
Run quality gates (if code changed) - Tests, linters, builds
-
Update issue status - Close finished work, update in-progress items
-
PUSH TO REMOTE - This is MANDATORY:
git pull --rebase git push git status # MUST show "up to date with origin" -
Clean up - Clear stashes, prune remote branches
-
Verify - All changes committed AND pushed
-
Hand off - Provide context for next session
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.
- 3d ago First seen · 68 lines · 588 tokens per session scan A df73bdb20c1c
biff AGENTS.md is an instructions file published in the GitHub repository punt-labs/biff (2 stars, last pushed today), licensed MIT. It adds 588 tokens to every session, about $0.0029 per session on Opus 5. A static security scan graded it A with 0 findings. It is 84% identical to dspy-skills AGENTS.md, differing in 35 lines, and is treated as a copy.
Other instructions, from other repositories
prfaq CLAUDE.md
Instructions for punt-labs/prfaq, covering how i write code, mandatory reading, no "pre-existing" excuse, standards and development workflow.
quarry CLAUDE.md
Instructions for punt-labs/quarry, covering quarry, mandatory reading, architecture, how a query works and how ingestion works.
vox CLAUDE.md
Instructions for punt-labs/vox, covering vox, mandatory reading, architecture, how synthesis works and key architectural boundary: daemon vs. clients.
beadle CLAUDE.md
Instructions for punt-labs/beadle, covering beadle, what beadle is, identity, no "pre-existing" excuse and standards.
vox AGENTS.md
Instructions for punt-labs/vox, covering agent instructions, quick reference and landing the plane (session completion).
quarry copilot-instructions.md
Instructions for punt-labs/quarry, covering copilot code review instructions, what to focus on, what not to flag, do not suggest and context.