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-researchgit 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-research)<a href="https://agentmods.dev/skills/001tmf/blatant-why/by-research"><img src="https://agentmods.dev/badge/skills/001tmf/blatant-why/by-research/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-research"><img src="https://agentmods.dev/badge/skills/001tmf/blatant-why/by-research.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, 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 Memory Poisoning · line 618 Skill attempts to fill the context window with filler content, displacing legitimate instructions and safety constraints. This can degrade agent performance or bypass safety boundaries.Fix: Implement context-window management that detects and rejects padding or stuffing attempts. Prioritize system instructions over user-injected content.
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.08722 |
| Opus 5 | $0.00002 | $0.04361 |
| Sonnet 5 | $0.00001 | $0.01744 |
| Haiku 4.5 | $0.00000 | $0.00872 |
Grade A, and why
by-research 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 10d 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 — 692 lines — stays where its author put it; the contents beside it link to each section on GitHub.
BY Research Skill
Thorough target research before design prevents wasted compute and failed campaigns. This skill defines an 8-phase pipeline that retrieves, validates, and packages research findings with quality gates and anti-drift checkpoints at every stage.
When to Use This Skill
Use this skill when you have:
- ✅ A protein target name or identifier (UniProt accession, gene name, PDB ID, or common name)
- ✅ A new design campaign starting — research is always step 1 before planning
- ✅ A need to characterize prior art — existing antibodies, nanobodies, or designed binders
- ✅ A target with unknown or partially characterized epitopes — needs hotspot identification from literature + structure
- ✅ A need to choose modality or scaffold — research informs VHH vs scFv vs de novo
- ✅ An interrupted research session — resume from
research_progress.jsoncheckpoint
Do NOT use this skill when:
- ❌ You already have a validated target report in the campaign directory → load it instead of re-researching
- ❌ You are scoring or filtering existing designs → use
by-scoringorby-screening - ❌ You are predicting structure of a known sequence → use Protenix directly (no literature needed)
- ❌ You need lab submission logistics → use
by-deploy-computeor the lab-submission flow - ❌ The user wants ranked design results → use
by-display/resultsskill - ❌ You need a one-off database lookup (single PDB fetch) → call the MCP tool directly, no 8-phase overhead
Quick Start
User: "Research TNF-alpha for a nanobody design campaign."
Agent:
1. Phase 1 SCOPE → writes research/scope.json (target=TNF-alpha, modality=VHH, depth=quick)
2. Phase 2 PLAN → writes research/research_plan.json
3. Phase 3 RETRIEVE → calls 4 research_* MCP tools in parallel, writes sources.json
4. Phase 4 TRIANGULATE → writes validated_findings.json
5. Phase 5 SYNTHESIZE → drafts research.md
6. Phase 6 CRITIQUE → 3 personas, writes critique.json
7. Phase 7 REFINE → closes gaps, updates sources.json + validated_findings.json
8. Phase 8 PACKAGE → writes research.md + recommended_hotspots.json + design_recommendation.json
Expected: 10-15 sources, 3+ HIGH confidence findings, 5-10 hotspot residues,
design_recommendation.json with modality/protocol/tier ready for campaign-manager.
What ships with it
6 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.
- 10d ago First seen · 692 lines · 3 tokens per session scan A 55a2c45bfec2
by-research is a skill published in the GitHub repository 001TMF/blatant-why (114 stars, last pushed 24d ago), licensed MIT. It adds 3 tokens to every session and 8,722 once invoked, about $0.0000 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 skills, from other repositories
statistical-modeling
Statistical modeling and machine learning for biomarker discovery, survival analysis, classification, regression, and model interpretation.
genomic-variants
Analysis of called genomic variants — filtering, annotation, GWAS, and population-genetics summaries from VCF and PLINK-format data.
bulk-transcriptomics
Bulk RNA-seq and microarray differential expression analysis including method selection, batch correction, and complex experimental designs.
chromatin-regulation
Chromatin regulation analysis from called peaks and count matrices — differential binding, signal summarisation, peak annotation, and scATAC-seq.
spatial-omics
Spatial transcriptomics and spatial proteomics analysis covering technology-specific workflows, spatial statistics, deconvolution, and niche analysis.
drug-repurposing
Systematic drug repurposing via signature matching, target-based analysis, network proximity, genetic evidence scoring, and clinical evidence mining.