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 skills add HolobiomicsLab/asb-skill-collections --skill bam-file-coordinate-sorting-verificationgit clone --depth 1 https://github.com/HolobiomicsLab/asb-skill-collectionsWrote 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/holobiomicslab/asb-skill-collections/bam-file-coordinate-sorting-verification)<a href="https://agentmods.dev/skills/holobiomicslab/asb-skill-collections/bam-file-coordinate-sorting-verification"><img src="https://agentmods.dev/badge/skills/holobiomicslab/asb-skill-collections/bam-file-coordinate-sorting-verification/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/holobiomicslab/asb-skill-collections/bam-file-coordinate-sorting-verification"><img src="https://agentmods.dev/badge/skills/holobiomicslab/asb-skill-collections/bam-file-coordinate-sorting-verification.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00067 | $0.01341 |
| Opus 5 | $0.00034 | $0.00671 |
| Sonnet 5 | $0.00013 | $0.00268 |
| Haiku 4.5 | $0.00007 | $0.00134 |
Grade A, and why
bam-file-coordinate-sorting-verification 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 11d 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 — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.
BAM file coordinate sorting verification
Summary
Verify that input BAM files are coordinate-sorted before preprocessing with SnapATAC2's pp.make_fragment_file, ensuring compatibility with fragment file generation and correct output of chromatin accessibility data.
When to use
Before invoking pp.make_fragment_file on a BAM file from alignment or external sources, especially when the BAM's sort order is unknown or when integrating BAM files from multiple sequencing platforms (10X, standard genomics pipelines, or custom aligners) into a unified SnapATAC2 analysis.
When NOT to use
- Input is already a fragment file (BED.gz, .zst, or TSV) — coordinate sorting verification is only needed for BAM inputs.
- Using preprocessing pipelines that auto-sort BAM files internally (e.g., precellar) — verify documentation first.
- Input BAM is from a tool that streams coordinate-sorted output by design — may skip explicit verification if tool documentation guarantees sort order.
Inputs
- BAM file (aligned single-cell ATAC-seq reads with optional cell barcodes in tags)
- SAM/BAM header or file metadata indicating current sort order
Outputs
- Confirmation of coordinate sort order (e.g., samtools view header output or sort validation report)
- Re-sorted BAM file (if input was unsorted or query-name sorted)
How to apply
Check BAM file headers using standard tools (samtools view -H) to confirm the @HD line contains SO:coordinate, or verify coordinate sort order by spot-checking that genomic positions increase monotonically across reads. If the BAM is unsorted or sorted by read name (SO:queryname), re-sort it using samtools sort -o output.bam input.bam before passing to pp.make_fragment_file. The pp.make_fragment_file function expects coordinate-sorted input and will produce compressed fragment files (BED.gz or .zst format) containing fragment coordinates, cell barcodes, and quality metrics only when the input is correctly ordered; misalignment of input sort order will compromise fragment boundary detection and barcode grouping.
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.
- 11d ago First seen · 98 lines · 67 tokens per session scan A 7c9dc4b21716
bam-file-coordinate-sorting-verification is a skill published in the GitHub repository HolobiomicsLab/asb-skill-collections (15 stars, last pushed 5d ago), licensed Apache-2.0. It adds 67 tokens to every session and 1,341 once invoked, about $0.0003 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
decision-curve-analysis
Use when evaluating the clinical utility of a binary prediction model from a single clinical CSV file by fitting a logistic decision-curve model, plotting decision and clinical-impact curves, and exporting summary outputs. NOT for: survival calibration, ROC-only discrimination analysis, nomogram construction, or…
elastic-net-feature-selection
Use when selecting predictive genes or other molecular features from bulk expression matrices for binary case-vs-control classification with elastic net logistic regression, including coefficient path and cross-validation plots. Trigger keywords: elastic net, glmnet, feature selection, binary classification…
external-model-validation
Use when validating an existing prognostic risk signature on an external bulk expression cohort with survival outcomes, producing risk scores, Kaplan-Meier curves, risk distribution plots, heatmap, and time-dependent ROC curves. NOT for: model training, feature selection, nomogram construction, calibration analysis…
wgcna-analysis
Use when building a weighted gene co-expression network from a bulk expression matrix and a sample group file, filtering variable genes by MAD, identifying co-expression modules with WGCNA, correlating modules with traits, and exporting module-level plots and gene tables. NOT for single-cell RNA-seq, differential…
medical-research-literature-reader-pro
A medical-research-native literature reading skill for users with clinical, bioinformatics, translational, and basic experimental backgrounds. Use this skill whenever a user wants to read, analyze, critique, or interpret a medical or scientific paper — whether they provide a PDF, abstract, DOI, PMID, or just a title.…
adverse-event-narrative
Generates CIOMS I-compliant ICSR narratives from adverse event case data for FDA and EMA regulatory submission. Includes temporal analysis, MedDRA coding, causality assessment using WHO-UMC or Naranjo criteria, and multi-format output.