by-plan-checker

by-plan-checker is an agent for Claude Code from 001TMF/blatant-why. It costs 32 tokens per session (1,032 once invoked), scanned A, original, MIT.

A review agent that checks a campaign plan before a user approves it. It examines the plan’s validation steps, costs, design type, settings, and scaffold choices.

In plain words
What is it for?
Use it to verify fold validation, compute and laboratory cost estimates, design-type selection, parameters, and scaffold reasoning.
Why use it?
It catches missing requirements, unsupported decisions, unsafe steps, and unrealistic costs before work begins.

Agent for Claude Code

Written for Claude Code: installed under .claude/.

Good fit Use it to verify fold validation, compute and laboratory cost estimates, design-type selection, parameters, and scaffold reasoning.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/001tmf/blatant-why/by-plan-checker
Install

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.

Clone the repo
git clone --depth 1 https://github.com/001TMF/blatant-why

Made for: Claude Code.

Wrote 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.

agentmods badge for by-plan-checker

README.md
[![agentmods](https://agentmods.dev/badge/agents/001tmf/blatant-why/by-plan-checker.svg)](https://agentmods.dev/agents/001tmf/blatant-why/by-plan-checker)
Your own site
<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>
Per session 32 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,032 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce 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

Measured 8d ago against content hash 9a1c26153f27, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

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.

templates/.claude/agents/by-plan-checker.md · 89 lines

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

  1. 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.

  2. 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
  3. 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)
  4. 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
  5. 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
  6. 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)

Read the full file on GitHub · 89 lines

Changes

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.

  1. 8d ago First seen · 89 lines · 32 tokens per session scan A 9a1c26153f27

Subscribe to this mod's changes

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.

Related

Other agents, from other repositories