route-selection

A comparison rule set for two workflows that create new protein binders from computational models. It helps compare the Proteina-Complexa route with the RFdiffusion, ProteinMPNN, and Boltz2 or OpenFold3 route.

In plain words
What is it for?
Use it to compare the two binder-design routes and choose one for a target and its constraints.
Why use it?
It helps choose a suitable workflow when a target or project has particular requirements.

Cursor rule

Install

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.

agentmods
npx agentmods add rules/nvidia-bionemo/bionemo-agent-toolkit/route-selection
Clone the repo
git clone --depth 1 https://github.com/NVIDIA-BioNeMo/bionemo-agent-toolkit
Per session 35 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 382 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin unknown No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00035 $0.00382
Opus 5 $0.00017 $0.00191
Sonnet 5 $0.00007 $0.00076
Haiku 4.5 $0.00003 $0.00038

Measured 3d ago against content hash 70b852f5f0ec, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

route-selection 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.

workflows/generative-protein-binder-design/references/route-selection.mdc · 26 lines

The source is not reproduced here

No licence file

A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.

Read it on GitHub

Changes

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.

  1. 3d ago First seen · 26 lines · 35 tokens per session scan A 70b852f5f0ec

Subscribe to this mod's changes

route-selection is a cursor rule published in the GitHub repository NVIDIA-BioNeMo/bionemo-agent-toolkit (444 stars, last pushed 6d ago), with no licence file. It adds 35 tokens to every session and 382 once invoked, about $0.0002 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.