by-screening

by-screening is a skill for Claude Code from 001TMF/blatant-why. It costs 3 tokens per session (9,840 once invoked), scanned A, original, MIT.

A screening workflow for protein-binder and antibody designs made by PXDesign or BoltzGen. It checks whether candidate sequences meet quality, safety-liability, and developability requirements before laboratory testing.

In plain words
What is it for?
Classifying designs as pass or fail, checking modification risks and developability, diagnosing batch failures, and grouping similar candidates before ranking them.
Why use it?
It prevents unscreened designs from being treated as ready for experiments and helps identify failed batches or unsuitable candidates.

Skill for Claude Code

Written for Claude Code: installed under .claude/.

Good fit Classifying designs as pass or fail, checking modification risks and developability, diagnosing batch failures, and grouping similar candidates before ranking them.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/001tmf/blatant-why/by-screening
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.

Any agent
npx skills add 001TMF/blatant-why --skill by-screening
Clone the repo
git clone --depth 1 https://github.com/001TMF/blatant-why

Made for: Claude Code.

Wrote 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.

agentmods badge for by-screening

README.md
[![agentmods](https://agentmods.dev/badge/skills/001tmf/blatant-why/by-screening/github.svg)](https://agentmods.dev/skills/001tmf/blatant-why/by-screening)
Your own site
<a href="https://agentmods.dev/skills/001tmf/blatant-why/by-screening"><img src="https://agentmods.dev/badge/skills/001tmf/blatant-why/by-screening/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for by-screening

Your own site · 80×15
<a href="https://agentmods.dev/skills/001tmf/blatant-why/by-screening"><img src="https://agentmods.dev/badge/skills/001tmf/blatant-why/by-screening.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 3 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 9,840 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original 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.1 $0.00003 $0.09840
Opus 5.5 $0.00001 $0.03936
Sonnet 5.5 $0.00001 $0.01968
Haiku 4.5 $0.00000 $0.00984

Measured 1mo ago against content hash 66644a94a85b, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

by-screening 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 1mo ago.

The scan reads SKILL.md. This mod also ships 3 executable files (scripts/generate_screening_report.py, scripts/parse_scores.py, scripts/screen_batch.py), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

templates/.claude/skills/by-screening/SKILL.md · 812 lines

How it starts

The opening of the file, as written. The whole thing — 812 lines — stays where its author put it; the contents beside it link to each section on GitHub.

BY Screening Skill

Comprehensive screening battery for evaluating protein binder and antibody designs produced by PXDesign and BoltzGen. This skill encodes all quality filters, scoring thresholds, liability checks, and developability assessments used to triage designs before experimental validation.

Always run the full screening pipeline before presenting final candidates to the user. Never present unscreened designs as ready for validation.


When to Use This Skill

Use by-screening when you have:

  • ✅ Raw design outputs from BoltzGen or PXDesign with refolding predictions (Protenix NPZ + scores)
  • ✅ A set of candidate sequences that need PASS/FAIL classification before lab submission
  • ✅ A campaign nearing the /by:approve-lab gate — screening MUST run first
  • ✅ Designs that need PTM liability and developability triage prior to ranking
  • ✅ A need to diagnose batch-level failures (all FAIL ipTM, all FAIL RMSD, etc.)
  • ✅ The need to apply diversity clustering before presenting top-N candidates

Don't use this skill for:

  • ❌ Computing raw scoring metrics → use by-scoring (ipSAE NPZ math, composite formula derivation, multi-seed aggregation)
  • ❌ Diagnosing root cause of a failed campaign at the strategy level → use by-failure-diagnosis (modality choice, scaffold selection, target druggability)
  • ❌ Generating designs → use boltzgen or pxdesign
  • ❌ Selecting which designs to advance to lab AFTER screening — that is the by-design-workflow orchestration step
  • ❌ Looking up reference epitopes or target biology → use by-research

Cross-skill hand-off:

Situation Skill to call
Need raw ipSAE/ipTM numbers from NPZ by-scoring first, then this skill
Need to apply PASS/FAIL filters to a batch by-screening (this skill)
Whole batch fails screening (>80% FAIL) by-failure-diagnosis for strategy correction
Designs pass screening, need rank/select by-screening Stage 2 + 3, then by-design-workflow

Read the full file on GitHub · 812 lines

Files

What ships with it

6 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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. 1mo ago First seen · 812 lines · 3 tokens per session scan A 66644a94a85b

Subscribe to this mod's changes

by-screening is a skill published in the GitHub repository 001TMF/blatant-why (119 stars, last pushed 9d ago), licensed MIT. It adds 3 tokens to every session and 9,840 once invoked, about $0.0000 per session on Opus 5.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.