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 fragment-length-prediction-and-extensiongit 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/fragment-length-prediction-and-extension)<a href="https://agentmods.dev/skills/holobiomicslab/asb-skill-collections/fragment-length-prediction-and-extension"><img src="https://agentmods.dev/badge/skills/holobiomicslab/asb-skill-collections/fragment-length-prediction-and-extension/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/fragment-length-prediction-and-extension"><img src="https://agentmods.dev/badge/skills/holobiomicslab/asb-skill-collections/fragment-length-prediction-and-extension.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.00028 | $0.01445 |
| Opus 5 | $0.00014 | $0.00723 |
| Sonnet 5 | $0.00006 | $0.00289 |
| Haiku 4.5 | $0.00003 | $0.00145 |
Grade A, and why
fragment-length-prediction-and-extension 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 9d 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 — 92 lines — stays where its author put it; the contents beside it link to each section on GitHub.
fragment-length-prediction-and-extension
Summary
Estimate the DNA fragment length (d) from ChIP-Seq data using cross-correlation analysis, then extend aligned reads to this length to generate accurate ChIP coverage tracks. This step is critical for converting point-wise read alignments into fragment-level signal representation.
When to use
After filtering duplicate reads from ChIP-Seq data but before generating pileup coverage tracks. Apply this skill when you have aligned ChIP reads in BED format and need to construct coverage BEDGRAPH files that reflect the actual DNA fragment distribution rather than single-end read positions.
When NOT to use
- Input reads are already paired-end (BEDPE format) — use the observed fragment length distribution from BEDPE instead of re-predicting.
- Fragment length is known a priori from sequencing metadata — skip prediction and use the known value directly with --extsize.
- Control sample is being processed — predictd should only be applied to ChIP data, not input/control data.
Inputs
- Filtered ChIP-Seq reads in BED format (e.g., CTCF_ChIP_200K.bed.gz)
- Genome size specification (e.g., 'hs' for human, or explicit bp count)
Outputs
- Predicted fragment length scalar d (integer, in base pairs)
- ChIP coverage BEDGRAPH track (genomic coordinates × extended fragment count)
How to apply
First, run macs3 predictd on the filtered ChIP sample using parameters -g hs (human genome size) and -m 5 50 (search fragment length range 5–50 bp) to estimate the dominant fragment length d from cross-correlation peaks. The tool analyzes the distribution of reads across the genome and returns a single scalar d value. Next, use macs3 pileup with the --extsize parameter set to d to extend each filtered ChIP read bidirectionally (or in a strand-aware manner) to the predicted fragment length. This produces a BEDGRAPH file where each genomic position reflects the number of extended fragments covering it, not raw reads. The predicted fragment length d should typically fall within the sequencing protocol's expected range (e.g., 150–200 bp for typical ChIP-Seq); anomalous values (< 50 bp or > 500 bp) warrant re-examination of sequencing quality and read filtering.
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.
- 9d ago First seen · 92 lines · 28 tokens per session scan A c90f009a8869
fragment-length-prediction-and-extension is a skill published in the GitHub repository HolobiomicsLab/asb-skill-collections (15 stars, last pushed 2d ago), licensed Apache-2.0. It adds 28 tokens to every session and 1,445 once invoked, about $0.0001 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-03.
Other skills, from other repositories
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…
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.
anatomy-quiz-master
Generate interactive anatomy quizzes for medical education with multiple.
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…