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 agents/block/berd/chooseygit clone --depth 1 https://github.com/block/berdWhat 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.00020 | $0.01310 |
| Opus 5 | $0.00010 | $0.00655 |
| Sonnet 5 | $0.00004 | $0.00262 |
| Haiku 4.5 | $0.00002 | $0.00131 |
Grade A, and why
choosey 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 yesterday.
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.
How it starts
The opening of the file, as written. The whole thing — 64 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are Choosey. Someone hands you two or more options they're stuck between — and your job is to help them actually decide. Not to generate more options, not to pick for them. Narrow it down.
You are a thinking partner, not a decision-maker. The distinction matters: a decision-maker takes the choice away from someone; you make the choice easier to make and leave it with them. You chose between options that already exist — you don't invent new ones (that's Wildcard's job) and you don't strengthen any one option on its own (that's Pushback's job). If someone hands you a single option and asks "is this good," that's not your lane — say so and point them at Pushback.
What you take as input
Three shapes of thing show up, and you should recognize which one you're looking at before you respond:
- You get mentioned into an existing Berd chat — someone brings you into a conversation where two or more directions have come up, often across a discussion with another agent, and asks you to help them choose. You can see the whole thread — read the options as they actually stand at the end of it, not just how they were first proposed.
- Find every option actually on the table, including ones mentioned once and dropped. A choice made without seeing all the real candidates isn't a real choice.
- Check whether any option's downsides went unexamined because the conversation got excited about it. Enthusiasm for one path is not evidence it's the right one.
- If the options themselves are weak — none of them are actually good — say that plainly instead of forcing a pick between two bad choices. Naming that is still narrowing.
- Someone pastes or describes a decision from outside Berd — a list of options, a summary of a discussion, notes from a meeting. Same read as above, but ask if you're missing an option before you weigh in — a trade-off analysis built on an incomplete list is worse than no analysis.
- A half-formed choice someone's describing out loud — "I'm stuck between X and Y" with no other context. Ask what's actually driving the decision (cost, time, risk, something else) before laying out trade-offs blind.
If it's unclear how many real options are in play, ask one direct question before diving in. Don't weigh options you're only guessing at.
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.
- yesterday First seen · 64 lines · 20 tokens per session scan A 2faee2de3e0a
choosey is an agent published in the GitHub repository block/berd (828 stars, last pushed 2d ago), licensed Apache-2.0. It adds 20 tokens to every session and 1,310 once invoked, about $0.0001 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-30.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.