Getting it into your agent
There is no command for this one: it runs only inside a plugin, and the catalogue could not identify which plugin ships it. The source is linked below.
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.
[](https://agentmods.dev/skills/001tmf/blatant-why/by-display)<a href="https://agentmods.dev/skills/001tmf/blatant-why/by-display"><img src="https://agentmods.dev/badge/skills/001tmf/blatant-why/by-display/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/001tmf/blatant-why/by-display"><img src="https://agentmods.dev/badge/skills/001tmf/blatant-why/by-display.svg" alt="Reviewed on agentmods" width="80" 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.00002 | $0.06310 |
| Opus 5 | $0.00001 | $0.03155 |
| Sonnet 5 | $0.00000 | $0.01262 |
| Haiku 4.5 | $0.00000 | $0.00631 |
Grade A, and why
by-display 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 9d 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 — 569 lines — stays where its author put it; the contents beside it link to each section on GitHub.
BY Display Patterns
Standard display formats for all campaign output. They use Unicode box-drawing characters and markdown that render natively in Claude Code's terminal. Never use ANSI escape codes in response text — they render as literal characters.
Every other BY skill (research, screening, scoring, campaign-manager, ...) calls
into these templates when it is time to talk to the user. This file is the
canonical source; the literal templates live in
references/output-format-spec.md so other
skills can copy them verbatim.
When to Use This Skill
Use this skill when you are:
- ✅ Rendering campaign status for
/by:status,/by:watch, or phase transitions - ✅ Formatting screening reports (liabilities, developability, structure scores)
- ✅ Showing ranked results for
/by:resultsor any final campaign output - ✅ Displaying errors or quota warnings that need user attention
- ✅ Presenting a checkpoint or safety gate that requires explicit user approval
- ✅ Streaming progress during long-running design/fold jobs
- ✅ Closing a phase — every major phase ends with a "Next Up" block
Do NOT use this skill when:
- ❌ You need to compute scores — that is
by-scoring; this skill only renders them - ❌ You need to run a screening battery — that is
by-screening - ❌ You need to decide what to do next — that is
by-campaign-manager/by-design-workflow - ❌ You need raw machine-readable JSON output for another tool — emit JSON directly, not the human-facing templates here
- ❌ You want to invent a new visual style — extend the templates here instead of forking them
Inputs
This skill is consumed by other skills. Inputs are the data objects to be rendered:
Required (one of):
- Campaign checkpoint object —
{ campaign_id, target, phases: [{name, status, time, details}, ...], current_phase }. Source:by-campaign-manager(campaign_state.json). - Ranked design list —
[{ design_id, composite, ipSAE, ipTM, pLDDT, liabilities, verdict }, ...]. Source:by-scoring/by-screening. - Screening report object —
{ design_id, liabilities: {...}, developability: {...}, structure: {...}, verdict }. Source:by-screening. - Progress event —
{ phase, status (◆/✓/✗), message, elapsed }. Source: any long-running skill. - Error object —
{ title, details, suggested_next }.
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 9d ago First seen · 569 lines · 2 tokens per session scan A cb1a08a94e8a
by-display is a skill published in the GitHub repository 001TMF/blatant-why (114 stars, last pushed 23d ago), licensed MIT. It adds 2 tokens to every session and 6,310 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 skills, from other repositories
alphafold
Skill for protein structure prediction and analysis with AlphaFold. Use this skill whenever a user wants to predict or fetch a protein 3D structure, download structures from the AlphaFold Database (AFDB), run ColabFold for novel proteins, parse pLDDT confidence scores or PAE (predicted aligned error) from AlphaFold…
esm2
Skill for working with ESM2 protein language models from Meta FAIR. Use this skill whenever the user wants to generate protein embeddings or representations, score variant effects or predict mutation fitness, run contact prediction, or use ESMFold for structure prediction. Also trigger when the user mentions ESM2…
evo2
Skill for genomic sequence modeling and design with Evo2 from Arc Institute. Use this skill when a user wants to model or generate DNA sequences, score variant effects at single-nucleotide resolution, extract genomic embeddings, analyze mutations in non-coding or coding regions, design synthetic genomic elements…
rfdiffusion
Skill for de novo protein backbone generation with RFdiffusion from the Baker Lab (Institute for Protein Design). Use this skill when a user wants to design a new protein backbone from scratch, scaffold a functional motif into a new protein, design a protein binder against a target, generate symmetric oligomers…
alphafold3
Skill for structure prediction with AlphaFold 3 (AF3) from Google DeepMind. Use this skill when a user wants to predict the structure of a protein complex with ligands, DNA, or RNA; predict protein-ligand binding poses; model protein-nucleic acid interactions; use SMILES or CCD codes to specify small molecules; parse…
boltz
Skill for biomolecular structure and binding affinity prediction with Boltz-2. Use this skill when a user wants to predict protein-ligand complex structures, estimate binding affinities (IC50/ΔG), screen compound libraries, optimize lead compounds, model protein-DNA or protein-RNA interactions, specify binding pockets…