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 commands/001tmf/blatant-why/setupgit clone --depth 1 https://github.com/001TMF/blatant-whyWhat 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.00009 | $0.00638 |
| Opus 5 | $0.00005 | $0.00319 |
| Sonnet 5 | $0.00002 | $0.00128 |
| Haiku 4.5 | $0.00001 | $0.00064 |
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.
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_DIRorwhich protenix- PXDesign:
$PROTEUS_PROT_DIRorwhich pxdesign- boltzgen:
$PROTEUS_AB_DIRorwhich boltzgenGPU — run
nvidia-smiif 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:
- Tamarind Bio if API key is configured (preferred — free tier)
- Local GPU if NVIDIA GPU detected with sufficient VRAM (>=16GB)
- None — warn that no compute provider is available
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.
- 2d ago First seen · 80 lines · 9 tokens per session scan A 97727006c6e2
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.
Other commands, from other repositories
graphiti-health
Display unified real-time health status for Neo4j Aura and Graphiti services.
scaffold-fastmcp-v2
Scaffold a new FastMCP server with standard Life Sciences project structure following ADR-001 patterns.
graphiti-aura-stats
Generate production graph statistics for Neo4j Aura analytics and capacity planning.
graphiti-docker-stats
Generate development environment statistics for Docker Neo4j namespace management.
scaffold-fastmcp
Scaffold a new FastMCP server with standard Life Sciences project structure following ADR-001 patterns.
graphiti-verify
Run Day 1 verification sequence to confirm environment is working.