by:setup

A command for discovering and configuring a project's computing environment. It records available tools, graphics hardware, and relevant API keys in an environment profile.

In plain words
What is it for?
Use it to inventory installed protein-design tools, inspect NVIDIA GPU and CUDA details, and create or update the project's environment configuration.
Why use it?
It reveals which local programs and resources are available before work begins, helping agents choose suitable commands and identify missing dependencies or hardware.

Command for Claude Code

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.

agentmods
npx agentmods add commands/001tmf/blatant-why/setup
Clone the repo
git clone --depth 1 https://github.com/001TMF/blatant-why

Made for: Claude Code.

Per session 9 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 638 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00009 $0.00638
Opus 5 $0.00005 $0.00319
Sonnet 5 $0.00002 $0.00128
Haiku 4.5 $0.00001 $0.00064

Measured 2d ago against content hash 97727006c6e2, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

by:setup 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 2d 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/commands/by/setup.md · 80 lines

How it starts

The opening of the file, as written. The whole thing — 80 lines — stays where its author put it; the contents beside it link to each section on GitHub.

/setup — Environment Discovery and Configuration

Scan the local system and cloud endpoints to detect available tools, GPU resources, and API keys. Write a complete environment profile.

Instructions

Step 0: Read model profile

MODEL_PROFILE=$(cat .by/config.json 2>/dev/null | grep -o '"model_profile"[[:space:]]*:[[:space:]]*"[^"]*"' | grep -o '"[^"]*"$' | tr -d '"' || echo "balanced")

Model lookup for this command:

Agent quality balanced budget
by-environment sonnet sonnet haiku

Step 1: Ensure config directory

mkdir -p .by
if [ ! -f .by/config.json ]; then
  echo '{"model_profile": "balanced"}' > .by/config.json
fi

Step 2: Spawn by-environment agent

Delegate to a by-environment agent (model per profile table above):

Scan the compute environment and produce a complete inventory.

Local tools — check env vars and PATH for installed tools:

  • Protenix: $PROTEUS_FOLD_DIR or which protenix
  • PXDesign: $PROTEUS_PROT_DIR or which pxdesign
  • boltzgen: $PROTEUS_AB_DIR or which boltzgen

GPU — run nvidia-smi if available. Report:

  • GPU model, VRAM, driver version, CUDA version
  • If no GPU, note "CPU-only — cloud providers required"

Python environment — check for:

  • Python version (require 3.10+)
  • Key packages: torch, numpy, biopython, boltzgen

Cloud providers — check API key environment variables:

  • TAMARIND_API_KEY (Tamarind Bio)
  • ADAPTYV_API_KEY (Adaptyv Bio — lab submission)
  • Report configured/missing for each (NEVER log key values)

SSH tunnels — check for any active SSH tunnels to GPU nodes

Write complete results to .by/environment.json.

Step 3: Review environment report

Verify the agent produced valid environment.json with all required sections.

Step 4: Select default provider

Based on the environment scan, recommend a compute provider:

  1. Tamarind Bio if API key is configured (preferred — free tier)
  2. Local GPU if NVIDIA GPU detected with sufficient VRAM (>=16GB)
  3. None — warn that no compute provider is available

Read the full file on GitHub · 80 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. 2d ago First seen · 80 lines · 9 tokens per session scan A 97727006c6e2

Subscribe to this mod's changes

by:setup is a command published in the GitHub repository 001TMF/blatant-why (114 stars, last pushed 16d ago), licensed MIT. It adds 9 tokens to every session and 638 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.