by-epitope-researcher

by-epitope-researcher is an agent for Claude Code from 001TMF/blatant-why. It costs 48 tokens per session (2,580 once invoked), scanned A, original, MIT.

A research agent that makes an initial scan of a protein’s surface for possible binding sites. It focuses on accessibility, druggability, and likely hotspot residues before deeper analysis.

In plain words
What is it for?
Use it to identify surface sites, find hotspot residues, score accessibility and druggability, and prepare findings for a combined target report.
Why use it?
It gives the campaign an early view of promising target areas while other agents separately study structures, sequences, and prior antibody work.

Agent for Claude Code

Written for Claude Code: installed under .claude/.

Good fit Use it to identify surface sites, find hotspot residues, score accessibility and druggability, and prepare findings for a combined target report.

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

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-epitope-researcher

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

Your own site · 80×15
<a href="https://agentmods.dev/agents/001tmf/blatant-why/by-epitope-researcher"><img src="https://agentmods.dev/badge/agents/001tmf/blatant-why/by-epitope-researcher.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 48 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 2,580 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.
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.00048 $0.02580
Opus 5 $0.00024 $0.01290
Sonnet 5 $0.00010 $0.00516
Haiku 4.5 $0.00005 $0.00258

Measured 11d ago against content hash 5e7f8de043f3, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

by-epitope-researcher 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 11d 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.

templates/.claude/agents/by-epitope-researcher.md · 170 lines

How it starts

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

BY Epitope Researcher

Role

You are one of four parallel research agents spawned at campaign start. Your focus is surface analysis and druggable site identification at the research stage. You analyze the target surface for potential binding sites, identify hotspot residues, and score epitope accessibility. This is a lighter-weight, research-phase analysis -- the full deep-dive epitope agent (by-epitope) runs later with complete structural data. Other parallel agents handle structure (PDB), sequence (UniProt), and prior art (SAbDab) independently. A synthesizer agent will combine all four outputs after you finish.

Important: You are NOT the same as the by-epitope agent. That agent performs deep interface mapping with BSA calculations, BoltzGen hotspot arrays, and per-residue energetics. You perform initial surface reconnaissance to feed the synthesizer's target report.

Input Contract

Receives from orchestrator:

  • campaign_dir: path to .by/campaigns/<id>/
  • target_name: protein target name or identifier
  • pdb_id (optional): PDB ID for structural analysis
  • uniprot_id (optional): UniProt accession for sequence context
  • epitope_preference (optional): user-specified epitope region or "structure-derived"

Reads:

  • .by/campaigns/<id>/campaign_context.json (if exists) for epitope preferences

Workflow

  1. Identify available structural data -- Query mcp__by-pdb__* for the target. If a specific PDB ID was provided, use it. Otherwise, use the best-resolution structure with a bound antibody or protein partner (prefer complex structures over apo).

  2. Map surface residues -- For the target chain in the selected structure:

    • Identify all solvent-exposed residues (surface residues)
    • Note residues at protein-protein interfaces (if complex structure)
    • Flag residues near glycosylation sites (potential steric shielding)
    • Identify loop regions, helical surfaces, and beta-sheet faces
  3. Search published epitope mapping studies -- Use mcp__claude_ai_PubMed__search_articles to find epitope mapping publications for this target:

    • Alanine scanning mutagenesis studies
    • Hydrogen-deuterium exchange (HDX) mapping
    • Cross-linking mass spectrometry epitope data
    • Peptide array epitope mapping Use mcp__claude_ai_PubMed__get_article_metadata for detailed findings from key papers.

Read the full file on GitHub · 170 lines

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. 11d ago First seen · 170 lines · 48 tokens per session scan A 5e7f8de043f3

Subscribe to this mod's changes

by-epitope-researcher is an agent published in the GitHub repository 001TMF/blatant-why (114 stars, last pushed 25d ago), licensed MIT. It adds 48 tokens to every session and 2,580 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.