seqair: Instructions file for Claude Code

CLAUDE.md

seqair CLAUDE.md is an instructions file for Claude Code from Softleif/seqair. It costs 6,148 tokens per session, scanned A, original, Apache-2.0.

A repository instruction set for seqair, a Rust library for reading biological sequence files such as BAM, SAM, CRAM, and FASTA and producing pileup data. It documents coding rules, architecture, specifications, and testing conventions.

In plain words
What is it for?
Use it when modifying seqair code, its related Rust types, tracey specifications, or tests, especially when preserving the project's strict safety and style rules.
Why use it?
It gives an AI coding agent project-specific rules that general Rust guidance would not provide. This helps keep changes consistent with the repository's error handling, type design, and specification links.

Instructions file for Claude Code

Written for Claude Code: the file is CLAUDE.md.

This is Softleif/seqair's own configuration. It tells Claude Code how to work on seqair itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything seqair configures →

Reuse

Borrowing it

Nothing to install: this file belongs to Softleif/seqair. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/Softleif/seqair/main/CLAUDE.md
Clone the repo
git clone --depth 1 https://github.com/Softleif/seqair

Made for: Claude Code.

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.

agentmods badge for seqair CLAUDE.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/softleif/seqair/claude-md/github.svg)](https://agentmods.dev/instructions/softleif/seqair/claude-md)
Your own site
<a href="https://agentmods.dev/instructions/softleif/seqair/claude-md"><img src="https://agentmods.dev/badge/instructions/softleif/seqair/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.

agentmods 80×15 button for seqair CLAUDE.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/softleif/seqair/claude-md"><img src="https://agentmods.dev/badge/instructions/softleif/seqair/claude-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 6,148 This file is loaded in full into every session.
When invoked 6,148 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.06148 $0.06148
Opus 5.5 $0.02459 $0.02459
Sonnet 5.5 $0.01230 $0.01230
Haiku 4.5 $0.00615 $0.00615

Measured 2d ago against content hash 098272c39ee5, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

seqair 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 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.

CLAUDE.md · 142 lines

How it starts

The opening of the file, as written. The whole thing — 142 lines — stays where its author put it; the contents beside it link to each section on GitHub.

seqair

Pure-Rust BAM/SAM/CRAM/FASTA reader + pileup engine. I/O backend for rastair.

Workspace: crates/seqair (readers, pileup, BGZF, CRAM) and crates/seqair-types (Base, BaseQuality, MappingQuality, ModProbability, Strand, Phred, Probability, RmsAccumulator, RegionString, Pos/QPos).

Tracey specs

Specs in docs/spec/*.md with r[rule.id]. Code: // r[impl rule.id], tests: // r[verify rule.id]. Use the tracey skill. Add spec rules before implementing; update specs when changing behavior.

Coding style

Expert Rust. Modern idioms. Types are the primary abstraction.

  • Correctness and clarity first. Comments explain "why" only.
  • No mod.rs — use src/some_module.rs.
  • No unwrap() — propagate with ?.
  • No indexing — use .get(). If indexing is unavoidable, #[allow(clippy::indexing_slicing)] + debug_assert!.
  • No let _ = on fallible ops — propagate, log with warn!, or handle.
  • No from_utf8_lossy — use from_utf8()? with typed errors.
  • Error enums: one per module, typed fields only (never String), #[from] for wrapping. Never use io::Error::other("message") — add a typed variant instead. Hierarchy: BgzfError → BamHeaderError/BaiError → BamError; BamWriteError (parallel to BamError for the write path); FaiError/GziError → FastaError; FormatDetectionError → ReaderError; VcfHeaderError/VcfEncodeError/AllelesError → VcfError.
  • color_eyre for errors, tracing for logging.
  • Sequence names are SmolStr.
  • Tests: prefer cargo nextest run (parallel test-binary execution; ~8× faster than cargo test on this repo, config in .config/nextest.toml). Doctests aren't run by nextest — append cargo test --doc --quiet when you need to cover them. Prefer property-based tests with hegel (hegeltest) where applicable: #[hegel::test] fn f(tc: TestCase) with tc.draw(gs::..), #[hegel::composite] for custom generators, plain assert!/assert_eq!, tc.assume(..) to reject a case. Case counts live in hegel.toml; pin an expensive test with #[hegel::test(test_cases = crate::pinned::cases(N))] (integration tests add #[path = "../src/pinned.rs"] mod pinned;) so SEQAIR_PINNED_CASES=N can still override it — a bare test_cases = N beats HEGEL_TEST_CASES. Prefer constructing inputs in the shape you need over rejecting them — a rejection loop makes hegel's smallest generated input large and its shrinking useless. Round-trip tests against noodles and bcftools are the strongest validation — always add them for new output formats. Avoid tautological tests — don't verify code using a copy of the same logic (e.g., compute expected bin with the same reg2bin). Use independent oracles. For tests that write temp files (e.g., bcftools round-trips), use the tempfile crate (tempfile::NamedTempFile) rather than std::env::temp_dir().join(...) to avoid filename collisions under parallel test execution.
  • SmallVec in this project uses 2-arg form SmallVec<T, N> (not SmallVec<[T; N]>).
  • No silent as i32/as u32 truncation at serialization boundaries — use i32::try_from() or equivalent with typed errors. At allocation boundaries (parsing untrusted counts), apply practical upper bounds matching real-world data, not format maximums (i32::MAX is not a limit). See r[io.writer_limits] and r[io.fuzz.alloc_limits] in the general spec.

Read the full file on GitHub · 142 lines

Changes

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.

  1. 2d ago Changed · +9 tokens per session 098272c39ee5
  2. 20d ago Changed · +124 tokens per session a4d3815ad1bc
  3. 28d ago Changed · -1 tokens per session 192d5c3381c5
  4. 1mo ago Changed · +26 lines · +2,568 tokens per session f8b9336d7262
  5. 1mo ago Changed · +294 tokens per session ee340ee67470
  6. 1mo ago Changed · +2 lines · +152 tokens per session 5c45b4f73d7a
  7. 1mo ago First seen · 114 lines · 3,002 tokens per session scan A dd77b65cf1bb

Subscribe to this mod's changes

seqair CLAUDE.md is an instructions file published in the GitHub repository Softleif/seqair (31 stars, last pushed today), licensed Apache-2.0. It adds 6,148 tokens to every session, about $0.0246 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-09-04.

Related

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).

microsoft/vscode · 9,715 tokens

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.

vercel/next.js · 7,461 tokens

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).

microsoft/vscode · 5,262 tokens

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.

langchain-ai/langchain · 4,680 tokens

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).

microsoft/vscode · 2,750 tokens

deno copilot-instructions.md

Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.

denoland/deno · 3,077 tokens