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 skills add 001TMF/blatant-why --skill 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/skills/001tmf/blatant-why/by-knowledge)<a href="https://agentmods.dev/skills/001tmf/blatant-why/by-knowledge"><img src="https://agentmods.dev/badge/skills/001tmf/blatant-why/by-knowledge/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.
<a href="https://agentmods.dev/skills/001tmf/blatant-why/by-knowledge"><img src="https://agentmods.dev/badge/skills/001tmf/blatant-why/by-knowledge.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 6 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Rogue Agent · line 41 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
- medium Rogue Agent · line 124 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
- medium Rogue Agent · line 164 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
- medium Rogue Agent · line 238 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
- low MCP Rug Pull · line 86 pip install without ==version installs the latest release, which could include malicious changes.Fix: Pin the version: pip install package==1.2.3
- low MCP Rug Pull · line 248 pip install without ==version installs the latest release, which could include malicious changes.Fix: Pin the version: pip install package==1.2.3
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.1 | $0.00003 | $0.04440 |
| Opus 5.5 | $0.00001 | $0.01776 |
| Sonnet 5.5 | $0.00001 | $0.00888 |
| Haiku 4.5 | $0.00000 | $0.00444 |
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 1mo 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 — 366 lines — stays where its author put it; the contents beside it link to each section on GitHub.
BY Knowledge Graph
Persistent structured memory that turns isolated campaigns into a learning system. Each campaign writes outcomes, top designs, and failure modes into a JSON-backed graph so the next campaign benefits from prior art without re-running compute.
The store is intentionally minimal: append-only JSON files, no server process, no embeddings — keyword overlap is enough for the scale we operate at (hundreds to low thousands of campaigns). Six MCP tools wrap the storage layer so every agent in the BY suite reads and writes through the same contract.
When to Use This Skill
Use this skill when:
- ✅ Starting a new campaign — query prior campaigns and scaffold rankings before committing compute
- ✅ Finishing a campaign — record outcomes, top designs, and any failure patterns
- ✅ Diagnosing low pass rates — search for matching failure patterns from prior campaigns
- ✅ Pre-flight parameter selection — call
knowledge_get_recommendationsto seed defaults - ✅ Periodic maintenance — run
knowledge_consolidateafter every 20-30 campaigns - ✅ Cross-target analysis — compare hit rates of a scaffold across target classes
Don't use this skill for:
- ❌ Storing raw design files — those live in the campaign directory (FASTA, PDB, CIF)
- ❌ Storing every design from a campaign — record the top 10-20 only (selectivity matters)
- ❌ Replacing the research dossier —
by-researchwritesresearch/research.md; this skill stores the summary - ❌ Per-job telemetry or compute logs — use
by-campaign-managercheckpoints instead - ❌ Free-form notes that have no entity to attach to — write them to
.claude/memory/directly
The graph is a long-lived asset. Be selective on writes; aggressive on queries.
Quick Start
# 1. Query prior art at campaign start
result = mcp__by_knowledge__knowledge_query_similar(
target_description="TNF-alpha cytokine homotrimer autoimmune",
modality="VHH",
top_k=5,
)
# 2. Record outcomes at campaign end (top 10-20 designs, not all of them)
mcp__by_knowledge__knowledge_store_campaign(
target="TNF-alpha",
modality="VHH",
parameters={"scaffold": "caplacizumab", "seeds": 4, "temperature": 0.7},
outcomes={
"hit_rate": 0.23,
"best_ipsae": 0.78,
"best_iptm": 0.85,
"screening_pass_rate": 0.18,
},
notes="Iter-2 hotspot refinement converged on Y56/R113",
designs=[
{"design_id": "tnf_001", "scaffold": "caplacizumab", "ipsae": 0.78, "iptm": 0.85, "status": "PASS"},
# ... up to ~20 top designs
],
)
What ships with it
4 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.
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.
- 1mo ago First seen · 366 lines · 3 tokens per session scan A 51817f993893
by-knowledge 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 4,440 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.
Other skills, from other repositories
cache
Use when the user wants to view, search, add, edit, prune, archive, or clear hyperflow memory entries. CRUD interface for .hyperflow/memory/ — never modifies source code, only memory files. Trigger with /hyperflow:cache, "show memory", "search memory for X", "clear memory", "what does hyperflow remember about Y".
shodh-memory
Persistent memory system for AI agents. Use this skill to remember context across conversations, recall relevant information, and build long-term knowledge. Activate when you need to store decisions, learnings, errors, or context that should persist beyond the current session.
agent-recall
Persistent compounding memory for AI agents. 5 default MCP tools: sessionstart, sessionend, remember, recall, check. Full surface: 6 tools with --full (adds checkaction); 13 tools with AREXTRAS=1 --full. Two-verb model: inhale (sessionstart) and exhale (sessionend). Correction-first memory with decision trail…
statistical-modeling
Statistical modeling and machine learning for biomarker discovery, survival analysis, classification, regression, and model interpretation.
chromatin-regulation
Chromatin regulation analysis from called peaks and count matrices — differential binding, signal summarisation, peak annotation, and scATAC-seq.
genomic-variants
Analysis of called genomic variants — filtering, annotation, GWAS, and population-genetics summaries from VCF and PLINK-format data.