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 bedgraph-format-parsing-and-validationgit 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/bedgraph-format-parsing-and-validation)<a href="https://agentmods.dev/skills/holobiomicslab/asb-skill-collections/bedgraph-format-parsing-and-validation"><img src="https://agentmods.dev/badge/skills/holobiomicslab/asb-skill-collections/bedgraph-format-parsing-and-validation/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/bedgraph-format-parsing-and-validation"><img src="https://agentmods.dev/badge/skills/holobiomicslab/asb-skill-collections/bedgraph-format-parsing-and-validation.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.00056 | $0.01482 |
| Opus 5 | $0.00028 | $0.00741 |
| Sonnet 5 | $0.00011 | $0.00296 |
| Haiku 4.5 | $0.00006 | $0.00148 |
Grade A, and why
bedgraph-format-parsing-and-validation 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 — 101 lines — stays where its author put it; the contents beside it link to each section on GitHub.
bedgraph-format-parsing-and-validation
Summary
Parse and validate UCSC bedGraph files to ensure they meet format requirements for sparse chromatin profiling analysis, particularly for CUT&RUN peak-calling workflows. This skill detects malformed coordinates, missing signal fields, and zero-signal regions that must be filtered before downstream peak-calling.
When to use
You have generated or received bedGraph files from paired-end sequencing (via bedtools genomecov or similar) and need to verify they conform to UCSC bedGraph format before passing them to peak-calling tools like SEACR. Use this when input bedGraphs have unknown provenance, were generated from custom pipelines, or have failed in downstream analysis.
When NOT to use
- Input is already a peak-called BED file with enriched regions; parse as standard BED3 or BED6 instead.
- Input is a single-end BAM or fragment file where read pair structure is unknown; cannot reliably convert to density-based bedGraph without pair information.
- Input is a different wiggle format (e.g., bedWig, variableStep); requires format-specific parser.
Inputs
- UCSC bedGraph file (tab-delimited: chr, start, end, signal)
- Paired-end BAM file (optional, for de novo bedGraph generation)
- Paired-end BED file with 5' and 3' read coordinates (optional)
Outputs
- Validated UCSC bedGraph file with zero-signal lines removed
- Parsed bedGraph dataframe or table (for downstream analysis)
- Coordinate and signal validation report
How to apply
Verify that bedGraph input adheres to UCSC bedGraph format (https://genome.ucsc.edu/goldenpath/help/bedgraph.html), checking that each line contains four tab-delimited fields: chromosome, start coordinate, end coordinate, and signal value. Filter out any bedGraph lines containing zero signal, as SEACR and similar tools expect bedGraphs that omit regions with zero coverage. Validate coordinate ordering (start < end) and signal values as numeric. If converting from BAM files, follow the paired-end fragment workflow: convert to bedpe format with bedtools bamtobed, extract 5' and 3' termini coordinates, sort, and generate the bedGraph using bedtools genomecov with the -bg flag to produce density across read pairs rather than individual reads.
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 · 101 lines · 56 tokens per session scan A 41d916705ad5
bedgraph-format-parsing-and-validation is a skill published in the GitHub repository HolobiomicsLab/asb-skill-collections (15 stars, last pushed today), licensed Apache-2.0. It adds 56 tokens to every session and 1,482 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.