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/softleif/seqair/claude-mdgit clone --depth 1 https://github.com/Softleif/seqairWrote 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/softleif/seqair/claude-md)<a href="https://agentmods.dev/instructions/softleif/seqair/claude-md"><img src="https://agentmods.dev/badge/instructions/softleif/seqair/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.03002 | $0.03002 |
| Opus 5 | $0.01501 | $0.01501 |
| Sonnet 5 | $0.00600 | $0.00600 |
| Haiku 4.5 | $0.00300 | $0.00300 |
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 today.
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 — 114 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, Strand, Phred, Probability, RmsAccumulator, RegionString).
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— usesrc/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 withwarn!, or handle. - No
from_utf8_lossy— usefrom_utf8()?with typed errors. - Error enums: one per module, typed fields only (never
String),#[from]for wrapping. Never useio::Error::other("message")— add a typed variant instead. Hierarchy:BgzfError→BamHeaderError/BaiError→BamError;BamWriteError(parallel toBamErrorfor the write path);FaiError/GziError→FastaError;FormatDetectionError→ReaderError;VcfHeaderError/VcfEncodeError/AllelesError→VcfError. color_eyrefor errors,tracingfor logging.- Sequence names are
SmolStr. - Tests: prefer
cargo nextest run(parallel test-binary execution; ~8× faster thancargo teston this repo, config in.config/nextest.toml). Doctests aren't run by nextest — appendcargo test --doc --quietwhen you need to cover them. Preferproptestwhere applicable. 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 samereg2bin). Use independent oracles. For tests that write temp files (e.g., bcftools round-trips), use thetempfilecrate (tempfile::NamedTempFile) rather thanstd::env::temp_dir().join(...)to avoid filename collisions under parallel test execution. SmallVecin this project uses 2-arg formSmallVec<T, N>(notSmallVec<[T; N]>).- No silent
as i32/as u32truncation at serialization boundaries — usei32::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::MAXis not a limit). Seer[io.writer_limits]andr[io.fuzz.alloc_limits]in the general spec.
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.
- today First seen · 114 lines · 3,002 tokens per session scan A dd77b65cf1bb
seqair CLAUDE.md is an instructions file published in the GitHub repository Softleif/seqair (29 stars, last pushed today), licensed Apache-2.0. It adds 3,002 tokens to every session, about $0.0150 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-09-04.
Other instructions, from other repositories
deno CLAUDE.md
Claude Code instructions for denoland/deno, covering deno development guide, git workflow, high level overview, key directories and quick start.
compiler-explorer AGENTS.md
AGENTS.md instructions for compiler-explorer/compiler-explorer, covering agents.md, build & test commands, important workflow requirements, style guidelines and architecture guidelines.
moon AGENTS.md
AGENTS.md instructions for moonrepo/moon, covering agents.md, repository layout, prerequisites, rust workflow and conventions.
Better-Fullstack AGENTS.md
AGENTS.md instructions for Marve10s/Better-Fullstack, covering guidelines, web ui, workflow and bun.
pixtuoid CLAUDE.md
Claude Code instructions for IvanWng97/pixtuoid, covering claude.md, what this is, layout, build & test and workflow.
YSCV AGENTS.md
AGENTS.md instructions for enthropy7/YSCV, covering agents.md — rules for ai coding agents working on yscv, responsibility, 0. read these first, in order, 1. the five commandments and 2. the workflow.