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.
npx agentmods add agents/001tmf/blatant-why/by-knowledgegit clone --depth 1 https://github.com/001TMF/blatant-whyWrote 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.
[](https://agentmods.dev/agents/001tmf/blatant-why/by-knowledge)<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>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.
| Model | Per session | Once 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 |
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.
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:
-
Parse the query -- Determine what information is needed: similar campaigns, scaffold rankings, failure patterns, parameter recommendations, or target-specific history.
-
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)
-
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
-
Return structured response -- Format findings for the requesting agent.
When storing new outcomes (post-campaign):
-
Read campaign results -- Load final screening results and campaign metadata from
mcp__by-campaign__*. -
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
-
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.
-
Store failure records -- For failed designs, record the failure mode, parameter context, and any identified root cause.
-
Generate recommendations -- Update the recommendation model with new data points.
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.
- 4d ago First seen · 96 lines · 30 tokens per session scan A 130e7f3528cb
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.
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.
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…
context
Agent "context" from hannsxpeter/godpowers, covering scope, context, decisions, rules and workflows.
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.
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…
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…