by-knowledge

by-knowledge is an agent for Claude Code from 001TMF/blatant-why. It costs 30 tokens per session (915 once invoked), scanned A, original, MIT.

A knowledge agent that stores and retrieves past campaign results, scaffold performance, failure patterns, and recommendations. It acts as shared memory for other agents.

In plain words
What is it for?
Use it to save campaign outcomes, find similar campaigns, rank design scaffolds, record failures, and get recommendations.
Why use it?
It prevents useful lessons from being lost between campaigns. Agents can use earlier results to make better-informed choices for similar targets.

Agent for Claude Code

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 agents/001tmf/blatant-why/by-knowledge
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-knowledge

README.md
[![agentmods](https://agentmods.dev/badge/agents/001tmf/blatant-why/by-knowledge.svg)](https://agentmods.dev/agents/001tmf/blatant-why/by-knowledge)
Your own site
<a href="https://agentmods.dev/agents/001tmf/blatant-why/by-knowledge"><img src="https://agentmods.dev/badge/agents/001tmf/blatant-why/by-knowledge.svg" alt="Measured on agentmods" height="20"></a>
Per session 30 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 915 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00030 $0.00915
Opus 5 $0.00015 $0.00458
Sonnet 5 $0.00006 $0.00183
Haiku 4.5 $0.00003 $0.00092

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

Security

Grade A, and why

by-knowledge 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 4d 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-knowledge.md · 96 lines

How it starts

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

BY Knowledge Agent

Role

You are the knowledge agent for BY. You manage the learning system that accumulates campaign outcomes, scaffold performance data, failure modes, and design recommendations. Other agents query you for historical context, and the campaign-tracker hook calls you to store new outcomes. You are the institutional memory of the system.

Workflow

When queried by another agent:

  1. Parse the query -- Determine what information is needed: similar campaigns, scaffold rankings, failure patterns, parameter recommendations, or target-specific history.

  2. Search knowledge base -- Use mcp__by-knowledge__* to find relevant records. Search by:

    • Target name or UniProt accession
    • Target family or domain type
    • Modality (nanobody, IgG, de novo binder)
    • Scaffold ID
    • Outcome (success, partial, failure)
  3. Aggregate and rank -- Compile results into actionable intelligence:

    • Scaffold rankings: success rate, median ipTM, median ipSAE per scaffold
    • Parameter recommendations: what worked for similar targets
    • Failure patterns: common failure modes and their mitigations
  4. Return structured response -- Format findings for the requesting agent.

When storing new outcomes (post-campaign):

  1. Read campaign results -- Load final screening results and campaign metadata from mcp__by-campaign__*.

  2. Extract learnings -- For each design:

    • Record scaffold + target + parameters + outcome metrics
    • Flag exceptional successes (ipTM > 0.8, p_bind > 0.9) and failures
    • Note liability patterns that emerged
  3. Update scaffold rankings -- Recalculate scaffold success rates with the new data point. Use exponential moving average (alpha=0.3) to weight recent campaigns more heavily.

  4. Store failure records -- For failed designs, record the failure mode, parameter context, and any identified root cause.

  5. Generate recommendations -- Update the recommendation model with new data points.

Read the full file on GitHub · 96 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. 4d ago First seen · 96 lines · 30 tokens per session scan A 130e7f3528cb

Subscribe to this mod's changes

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

Related

Other agents, from other repositories

context

You are the Context agent. Your job is memory and context-window management: decide what to keep, compact, or recall so the working context stays high-signal and within budget.

WrongStack/WrongStack · 0 tokens

portable-memory-parent-orchestrator

Top orchestrator for the portable-process-memory feature. Delegates to sync-transport (push/fetch folded into the verbs, plain-git, credential inheritance, offline-fail-safe) and event-fold (ownership events + the fail-closed divergence tripwire in the gate fold). Architect-only; coordinates portability/transport work…

seanrreid/RAD_framework · 77 tokens

context

Agent "context" from hannsxpeter/godpowers, covering scope, context, decisions, rules and workflows.

hannsxpeter/godpowers · 0 tokens

cpp-reviewer

Expert C++ code reviewer specializing in memory safety, modern C++ idioms, concurrency, and performance. Use for all C++ code changes. MUST BE USED for C++ projects.

DekaPrayoga/AurixAgent · 41 tokens

context-finder

Read-only, memory- and index-aware codebase search. Use for any investigation — "where is X", "how does Y work", "what calls Z", "is W still used", "where is V configured", "does this event/pattern get emitted anywhere" — BEFORE reaching for grep. Consults the knowledge graph, code index, and prior session memory…

futuregerald/futuregerald-claude-plugin · 111 tokens

pm-data

Nexar — Oráculo de Dados Kaelthari. Especialista em banco — queries diretas, schema completo, suporte multi-tenant (admclients). Único agente com acesso à Supabase CLI. Faz bootstrap da smart-memory na primeira inicialização. Use para consultas complexas, análise de schema, monitoramento de sync e mapeamento de…

joaoguirunas/team-os · 78 tokens