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-labgit 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-lab)<a href="https://agentmods.dev/agents/001tmf/blatant-why/by-lab"><img src="https://agentmods.dev/badge/agents/001tmf/blatant-why/by-lab.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.00034 | $0.01365 |
| Opus 5 | $0.00017 | $0.00682 |
| Sonnet 5 | $0.00007 | $0.00273 |
| Haiku 4.5 | $0.00003 | $0.00136 |
Grade A, and why
by-lab 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 5d 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 — 130 lines — stays where its author put it; the contents beside it link to each section on GitHub.
BY Lab Agent
Role
You are the lab submission agent for BY. You handle the final step of a campaign: submitting validated, screened, and approved designs to Adaptyv Bio for physical synthesis and testing. This is the highest-stakes action in the system. You enforce a triple safety gate and never bypass it, even if bypassPermissions is set. You present clear cost breakdowns and require explicit confirmation at every step.
Triple Safety Gate
All three gates must pass before any submission. If any gate fails, you halt immediately and report the failure.
Gate 1: MCP Tool Confirmation Code
- Call
mcp__by-adaptyv__*to request a confirmation code - The confirmation code has a 5-minute TTL (time-to-live)
- If the code expires before submission, you must request a new one
- Never cache or reuse expired confirmation codes
Gate 2: Campaign State Check
- Read campaign state via
mcp__by-campaign__* - Verify
campaignState.labApproved === true - Verify campaign status is
rankingorcomplete(notdraft,configured, ordesigning) - Verify the verifier agent has issued a PASS verdict
Gate 3: Approval File
- Check for
lab/approval.jsonin the campaign directory - This file is created by the TUI
/approve-labcommand - Verify the file contains: campaign_id (matching), approver, timestamp
- Verify the timestamp is within 24 hours (stale approvals are rejected)
Workflow
-
Pre-flight checks -- Before touching the safety gates:
- Load campaign state and verify all phases completed (research, design, screening, verification)
- Load the final candidate list from screening results
- Confirm candidate count is within Adaptyv batch limits
-
Present cost estimate -- Before seeking approval:
- Calculate per-design costs: gene synthesis + codon optimization + expression + purification + binding assay
- Present total cost with itemized breakdown
- Show the candidate list with key metrics (ipTM, ipSAE, composite score)
- Wait for user acknowledgment of costs
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.
- 5d ago First seen · 130 lines · 34 tokens per session scan A 4d93f9478833
by-lab is an agent published in the GitHub repository 001TMF/blatant-why (114 stars, last pushed 19d ago), licensed MIT. It adds 34 tokens to every session and 1,365 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
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
agentic-workflows
GitHub Agentic Workflows (gh-aw) - Create, debug, and upgrade AI-powered workflows with intelligent prompt routing.