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/viewgit 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.00017 | $0.00676 |
| Opus 5 | $0.00009 | $0.00338 |
| Sonnet 5 | $0.00003 | $0.00135 |
| Haiku 4.5 | $0.00002 | $0.00068 |
Grade A, and why
by:view 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 3d 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 — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/view — View Protein Structure
Open a protein structure in ProteinView in a tmux split pane with FullHD rendering.
Instructions
Step 1: Resolve the input
The argument can be:
- PDB ID (4 chars, e.g.,
3DPL) — fetch from RCSB - File path (e.g.,
.by/campaigns/.../design_003.cif) — open directly - Design name (e.g.,
design_003) — search active campaign for matching CIF/PDB file
If a design name is given, find the file:
CAMPAIGN_DIR=$(cat .by/active_campaign 2>/dev/null)
FILE=$(find "$CAMPAIGN_DIR" -name "*${DESIGN_NAME}*.cif" -o -name "*${DESIGN_NAME}*.pdb" 2>/dev/null | head -1)
Step 2: Determine color scheme
Pick color based on context:
- If viewing a design with confidence data →
--color plddt - If viewing a multi-chain complex →
--color chain - If viewing a target structure →
--color structure - Default →
--color chain
Step 3: Open in tmux split
tmux split-window -h "proteinview '${FILE_OR_PDB}' --fullhd --color ${COLOR}; read -p 'Press Enter to close'"
If the input is a PDB ID (no file):
tmux split-window -h "proteinview --fetch ${PDB_ID} --fullhd --color ${COLOR}; read -p 'Press Enter to close'"
Step 4: Confirm to user
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
BY ► VIEWING: {name}
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Opened in tmux split pane (FullHD mode).
Color: {color scheme}
File: {path or PDB ID}
Controls: arrow keys to rotate, +/- to zoom, q to quit
Prerequisites
Check before running:
which proteinview >/dev/null 2>&1 || echo "NOT_INSTALLED"
echo "$TMUX" | grep -q "/" && echo "IN_TMUX" || echo "NOT_TMUX"
-
If
proteinviewnot installed: tell the user it's a separate tool and how to get it:ProteinView is not installed. It's a separate terminal protein viewer. Install: cargo install proteinview GitHub: https://github.com/001TMF/proteinviewThen stop. Do not proceed.
-
If not in tmux: tell the user this is a tmux feature:
/by:view requires tmux (uses split panes for the viewer). Start tmux first: tmux new -s byThen stop. Do not proceed.
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.
- 3d ago First seen · 84 lines · 17 tokens per session scan A 36dfce94557a
by:view is a command published in the GitHub repository 001TMF/blatant-why (114 stars, last pushed 17d ago), licensed MIT. It adds 17 tokens to every session and 676 once invoked, about $0.0001 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
run-archesweather
Guide the user through running ArchesWeather end-to-end on an AMD cluster.
run-mattergen
Guide the user through running MatterGen end-to-end on an AMD cluster via SLURM or Docker.
run-matey
Guide the user through training or inference with MATEY on AMD GPUs.
run-aurora
Guide the user through running Aurora (0.1° resolution) end-to-end on an AMD cluster.
run-semlaflow
Guide the user through generating 3D molecular structures with SemlaFlow on AMD GPUs.
add-recipe
Create or improve a recipe (inference, fine-tune, eval, etc.) for a model already in AI4Science Studio.