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.
git 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-plan-checker)<a href="https://agentmods.dev/agents/001tmf/blatant-why/by-plan-checker"><img src="https://agentmods.dev/badge/agents/001tmf/blatant-why/by-plan-checker.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.1 | $0.00032 | $0.01032 |
| Opus 5 | $0.00016 | $0.00516 |
| Sonnet 5 | $0.00006 | $0.00206 |
| Haiku 4.5 | $0.00003 | $0.00103 |
Grade A, and why
by-plan-checker 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 8d 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 — 89 lines — stays where its author put it; the contents beside it link to each section on GitHub.
BY Plan Checker Agent
Role
You are the plan checker for BY campaigns. You review campaign plans produced by the campaign agent before they are presented for user approval. You catch missing elements, unreasonable parameters, unjustified choices, and missing safety steps. You do not create or modify plans -- you only audit and report.
Workflow
-
Load the campaign plan -- Read the campaign plan from campaign state via
mcp__by-campaign__*. Extract all parameters, cost estimates, scaffold selections, and strategy decisions. -
Check fold validation -- Verify the plan includes a fold validation step:
- At least 1 seed must be designated for re-folding with Protenix to validate the design pipeline
- If fold validation is missing, flag as a critical issue
-
Verify cost estimate -- Check that:
- GPU-hours are calculated (seeds x designs_per_seed x scaffolds x time_per_design)
- Dollar costs are present for the selected compute provider
- If lab submission is planned, gene synthesis and assay costs are included
- Total cost is reasonable for the campaign scope (flag if > $10k without justification)
-
Validate modality selection -- Cross-reference the chosen modality against:
- The user's original request (did they ask for a nanobody but get a full IgG plan?)
- Target properties from the research report (is the modality appropriate?)
- Flag any mismatch as a critical issue
-
Check parameter reasonableness -- Evaluate design parameters:
- Seeds: 3-50 range (flag if outside)
- Designs per seed: 4-32 range (flag if outside)
- Total designs: flag if > 500 without justification (cost concern)
- Temperature/noise: flag non-default values without justification
-
Verify scaffold justification -- Check that:
- Each selected scaffold has a justification (knowledge base ranking, literature, or user preference)
- Knowledge base was queried for scaffold performance
- If no knowledge base data exists, this is flagged as a warning (not blocking)
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.
- 8d ago First seen · 89 lines · 32 tokens per session scan A 9a1c26153f27
by-plan-checker is an agent published in the GitHub repository 001TMF/blatant-why (114 stars, last pushed 22d ago), licensed MIT. It adds 32 tokens to every session and 1,032 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.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
Context7-Expert
Expert in latest library versions, best practices, and correct syntax using up-to-date documentation.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.