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 instructions/kmaneesh/biopython-mcp/claude-mdgit clone --depth 1 https://github.com/kmaneesh/biopython-mcpWrote 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/kmaneesh/biopython-mcp/claude-md)<a href="https://agentmods.dev/instructions/kmaneesh/biopython-mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/kmaneesh/biopython-mcp/claude-md.svg" alt="Measured on agentmods" 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 | $0.01210 | $0.01210 |
| Opus 5 | $0.00605 | $0.00605 |
| Sonnet 5 | $0.00242 | $0.00242 |
| Haiku 4.5 | $0.00121 | $0.00121 |
Grade A, and why
biopython-mcp 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 4d 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 — 156 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
Project Overview
This is a Model Context Protocol (MCP) server that exposes BioPython library capabilities as tools for AI assistants. It allows AI models to perform bioinformatics operations like sequence analysis, alignment, database access, structural analysis, and phylogenetics.
Development Commands
Setup
pip install -e ".[dev]"
Running the Server
biopython-mcp
# Or directly:
python -m biopython_mcp.server
Testing
# Run all tests with coverage
pytest
# Run specific test file
pytest tests/test_sequence.py
# Run specific test class or function
pytest tests/test_sequence.py::TestTranslateSequence
pytest tests/test_sequence.py::TestTranslateSequence::test_translate_simple_dna
Code Quality
# Format code (REQUIRED before commit)
black biopython_mcp/ tests/
# Lint code
ruff check biopython_mcp/ tests/
# Type checking
mypy biopython_mcp/
IMPORTANT: Always run black before committing to ensure code passes CI lint checks.
Quick pre-commit check:
black biopython_mcp/ tests/ && ruff check biopython_mcp/ tests/
Architecture
Tool Registration Pattern
The server uses FastMCP to expose BioPython functions as MCP tools. All tool functions follow this pattern:
- Tool modules (
src/sequence.py,src/alignment.py, etc.) contain individual tool functions - Each tool function returns a dictionary with
{"success": bool, ...}format - Central registration in
src/server.pyimports and registers all tools withmcp.tool()
To add a new tool:
- Create the function in the appropriate module (or create a new module)
- Ensure it returns a dict with
successfield - Import and register it in
src/server.pyusingmcp.tool()(your_function)
Error Handling Convention
All tool functions use try-except blocks and return error information in the response dict:
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.
- 4d ago First seen · 156 lines · 1,210 tokens per session scan A 59c1da5bec79
biopython-mcp CLAUDE.md is an instructions file published in the GitHub repository kmaneesh/biopython-mcp (3 stars, last pushed 7mo ago), licensed MIT. It adds 1,210 tokens to every session, about $0.0060 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-31.
Other instructions, from other repositories
py3plex copilot-instructions.md
Copilot instructions for SkBlaz/py3plex, covering github copilot instructions for py3plex, project overview, repository structure, key code patterns and network creation.
viral-ngs copilot-instructions.md
Copilot instructions for broadinstitute/viral-ngs, covering copilot instructions, quick reference, running tests and key files.
FaST-LMM AGENTS.md
Instructions for fastlmm/FaST-LMM, covering coding notes for agents, general policies, cross-repository release coordination, numerical correctness and error handling.
StatsPAI CLAUDE.md
Claude Code instructions for brycewang-stanford/StatsPAI, covering claude.md — statspai, 1. 项目定位, 2. 仓库结构, 3. 设计原则 and 4. 代码规范.
AWETrim AGENTS.md
Instructions for awegroup/AWETrim, covering awetrim — agent context, what this repo is, module status, physics references and symbol ↔ code name table.
jax-numerics-agent AGENTS.md
Instructions for quattro/jax-numerics-agent, covering agents.md, scope, source of truth, agent workflow and global install note.