by-scoring

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

A scoring and interpretation skill for protein and antibody designs. It explains measures such as ipSAE, ipTM, pLDDT, RMSD, and liability scores, which estimate structure quality and possible design problems.

In plain words
What is it for?
Use it to rank designs, set quality cutoffs for different design types, investigate failed screening runs, compare metrics, and check whether results remain reliable across multiple random runs.
Why use it?
It helps turn several, sometimes conflicting, measurements into a consistent comparison of candidate designs.

Skill for Claude Code

Written for Claude Code: installed under .claude/.

Good fit Use it to rank designs, set quality cutoffs for different design types, investigate failed screening runs, compare metrics, and check whether results remain reliable across multiple random runs.

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

README.md
[![agentmods](https://agentmods.dev/badge/skills/001tmf/blatant-why/by-scoring/github.svg)](https://agentmods.dev/skills/001tmf/blatant-why/by-scoring)
Your own site
<a href="https://agentmods.dev/skills/001tmf/blatant-why/by-scoring"><img src="https://agentmods.dev/badge/skills/001tmf/blatant-why/by-scoring/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-scoring

Your own site · 80×15
<a href="https://agentmods.dev/skills/001tmf/blatant-why/by-scoring"><img src="https://agentmods.dev/badge/skills/001tmf/blatant-why/by-scoring.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 10,441 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.10441
Opus 5.5 $0.00001 $0.04176
Sonnet 5.5 $0.00001 $0.02088
Haiku 4.5 $0.00000 $0.01044

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

Security

Grade A, and why

by-scoring 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/calc_ipsae.py, scripts/composite_score.py, scripts/plot_score_distributions.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-scoring/SKILL.md · 813 lines

How it starts

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

BY Scoring Skill

Interpret and apply BY custom scoring metrics for protein and antibody design. This skill covers ipSAE (interface Predicted Structural Accuracy Error) — the primary custom metric that differentiates BY from generic structure prediction tools — along with ipTM, pLDDT, RMSD, liability scoring, and the BY composite ranking formula.

ipSAE uses the open-source DunbrackLab formula (Dunbrack et al. 2025) with no proprietary dependencies. Use this skill whenever you need to score designs, interpret scoring output, troubleshoot disagreements between metrics, or advise on candidate ranking.


When to Use This Skill

Use this skill when:

  • ✅ Scoring designs after Protenix refolding — you have NPZ or confidence JSON output
  • ✅ Computing the BY composite score on a panel of screened designs
  • ✅ Explaining why two metrics (ipSAE vs ipTM) disagree on a candidate
  • ✅ Setting modality-specific thresholds (antibody vs nanobody vs de novo)
  • ✅ Diagnosing why an entire panel failed screening (zero LAB-READY)
  • ✅ Auditing whether a multi-seed result is stable or driven by one lucky seed
  • ✅ Interpreting asymmetric ipSAE (dt >> td or td >> dt)
  • ✅ Selecting the right PAE cutoff (10 A Protenix/AF3 vs 15 A AF2)

Don't use this skill for:

  • ❌ Generating designs — use the by-design-workflow skill instead
  • ❌ Running liability or developability screening directly — use the by-screening skill
  • ❌ Choosing which target to design against — use the by-research skill
  • ❌ Submitting candidates to a lab — use the by-lab agent (triple-gated)
  • ❌ Predicting raw structures — use the protenix skill

Quick Start

Compute ipSAE for a single Protenix output:

# JSON confidence file (Protenix /summary_confidence.json)
python scripts/calc_ipsae.py \
    --pae confidence.json \
    --chains confidence.json \
    --design A --target B \
    --pae-cutoff 10.0

# Or run the worked numerical example from references/
python scripts/calc_ipsae.py --example
# Expected: ipsae_min = 0.0396

Read the full file on GitHub · 813 lines

Files

What ships with it

7 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 · 813 lines · 3 tokens per session scan A 8698b24c6a5a

Subscribe to this mod's changes

by-scoring 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 10,441 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.