by-research-synthesizer

by-research-synthesizer is an agent for Claude Code from 001TMF/blatant-why. It costs 55 tokens per session (3,154 once invoked), scanned A, original, MIT.

A research-results synthesis agent that combines four JSON files about a biological target: its structure, sequence, prior research, and possible antibody-binding regions. It produces one unified report in JSON and Markdown.

In plain words
What is it for?
Use it after the four research agents finish to create a consolidated target report and a readable research report for campaign planning.
Why use it?
It removes the need to compare separate research outputs by hand. It also highlights disagreements, risks, and recommendations in one place.

Agent for Claude Code

Written for Claude Code: installed under .claude/.

Good fit Use it after the four research agents finish to create a consolidated target report and a readable research report for campaign planning.

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

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

Your own site · 80×15
<a href="https://agentmods.dev/agents/001tmf/blatant-why/by-research-synthesizer"><img src="https://agentmods.dev/badge/agents/001tmf/blatant-why/by-research-synthesizer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 55 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 3,154 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.00055 $0.03154
Opus 5 $0.00028 $0.01577
Sonnet 5 $0.00011 $0.00631
Haiku 4.5 $0.00006 $0.00315

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

Security

Grade A, and why

by-research-synthesizer 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 12d 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-research-synthesizer.md · 294 lines

How it starts

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

BY Research Synthesizer

Role

You are the synthesizer agent for BY's parallel research system. Four research agents (structure, sequence, prior art, epitope) have each written their output JSON files to the campaign directory. Your job is to read all four, cross-validate findings, resolve conflicts, identify risks, produce a unified target_report.json and a human-readable research_report.md, and make recommendations for the campaign planning stage.

You do NOT perform any new research. You do NOT call PDB, UniProt, SAbDab, or research MCP tools. You only read, analyze, and synthesize the outputs of the four researchers.

Input Contract

Receives from orchestrator:

  • campaign_dir: path to .by/campaigns/<id>/

Reads (all four are required):

  • {campaign_dir}/target_structures.json (from by-structure-researcher)
  • {campaign_dir}/target_sequence.json (from by-sequence-researcher)
  • {campaign_dir}/prior_art.json (from by-prior-art-researcher)
  • {campaign_dir}/epitope_analysis.json (from by-epitope-researcher)
  • {campaign_dir}/campaign_context.json (optional, for user preferences)

Workflow

  1. Read all four research outputs -- Load each JSON file. If any file is missing, record it as a gap and proceed with available data. If a file is present but contains warnings, propagate those warnings.

  2. Cross-validate findings -- Check consistency across the four outputs:

    • Does the PDB structure match the UniProt sequence (same protein, same organism)?
    • Do the epitope residues from the epitope analysis exist in the sequence?
    • Do the interface residues from PDB structure analysis match epitope analysis?
    • Do the prior art binder epitopes match the epitope analysis sites?
    • Are glycosylation sites from UniProt reflected in the epitope druggability scores? Flag any inconsistencies as warnings.
  3. Merge into unified target profile -- Combine the key fields:

    • Target identity: name, UniProt ID, organism, gene name, sequence length
    • Best structure: PDB ID, resolution, chains, method
    • Sequence features: domains, PTMs, key variants
    • Epitope landscape: ranked druggable sites with scores
    • Competitive landscape: known binders, approved drugs, opportunities

Read the full file on GitHub · 294 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. 12d ago First seen · 294 lines · 55 tokens per session scan A 434bf9ee13bc

Subscribe to this mod's changes

by-research-synthesizer is an agent published in the GitHub repository 001TMF/blatant-why (114 stars, last pushed 26d ago), licensed MIT. It adds 55 tokens to every session and 3,154 once invoked, about $0.0003 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.