Borrowing it
Nothing to install: this file belongs to 001TMF/blatant-why. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/001TMF/blatant-why/master/CLAUDE.mdgit clone --depth 1 https://github.com/001TMF/blatant-whyWrote 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/instructions/001tmf/blatant-why/claude-md)<a href="https://agentmods.dev/instructions/001tmf/blatant-why/claude-md"><img src="https://agentmods.dev/badge/instructions/001tmf/blatant-why/claude-md/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/instructions/001tmf/blatant-why/claude-md"><img src="https://agentmods.dev/badge/instructions/001tmf/blatant-why/claude-md.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.00634 | $0.00634 |
| Opus 5.5 | $0.00254 | $0.00254 |
| Sonnet 5.5 | $0.00127 | $0.00127 |
| Haiku 4.5 | $0.00063 | $0.00063 |
Grade A, and why
blatant-why CLAUDE.md 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 1mo 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 — 64 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md — BY (Blatant-Why) Dev Context
About This File
This file provides development-time context for working ON the BY codebase itself. The canonical agent identity is defined in templates/CLAUDE.md. During development, Claude works hands-on — editing code, running tests, managing git. For campaign-related behavior, see the template.
Canonical identity: templates/CLAUDE.md defines BY as a hands-on protein design agent who uses MCP tools directly. This root file must never contradict that identity.
Dev Guidelines
Before making changes:
- Analyze the existing codebase for relevant files, services, and patterns
- Include specific file paths when scoping work
- Default to extending existing files over creating new ones
- If a new file is proposed, require justification for why existing code cannot be extended
Git Workflow
- Create feature branches before starting work
- Review all output before staging
- Write clear commit messages summarizing what was done and why
- Never commit code that has not been reviewed
Review Checklist
Before accepting any changes:
- Follows existing codebase patterns and architecture
- Reuses existing code where possible (no unnecessary new files)
- Meets the acceptance criteria
- No regressions or broken imports
- Clean, consistent with project style
Reference: Campaign Agent Teams
These agent teams are defined in templates/.claude/agents/. See templates/CLAUDE.md for the canonical campaign workflow.
| Agent | Role | MCP Servers |
|---|---|---|
| Research | Target analysis, literature, prior art | pdb, uniprot, sabdab, research |
| Design | Generate designs via cloud or local | pdb, screening, tamarind, campaign |
| Screening | Score, filter, rank designs | screening, campaign |
| Lab Integration | Submit to Adaptyv Bio (GATED) | adaptyv |
Campaign Workflow
- RESEARCH — spawn Research Agent for target analysis
- COST ESTIMATE — compute costs (seeds x designs x scaffolds)
- DESIGN — spawn Design Agent + start Monitor
- SCREENING — spawn Screening Agent
- RANKING — composite score, diversity selection
- LAB (GATED) — only with explicit /approve-lab
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.
- 1mo ago First seen · 64 lines · 634 tokens per session scan A e69d476c2e02
blatant-why CLAUDE.md is an instructions file published in the GitHub repository 001TMF/blatant-why (119 stars, last pushed 9d ago), licensed MIT. It adds 634 tokens to every session, about $0.0025 per session on Opus 5.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 instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.