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 chip-seq-signal-pileup-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/chip-seq-signal-pileup-extension)<a href="https://agentmods.dev/skills/holobiomicslab/asb-skill-collections/chip-seq-signal-pileup-extension"><img src="https://agentmods.dev/badge/skills/holobiomicslab/asb-skill-collections/chip-seq-signal-pileup-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/chip-seq-signal-pileup-extension"><img src="https://agentmods.dev/badge/skills/holobiomicslab/asb-skill-collections/chip-seq-signal-pileup-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.00048 | $0.01916 |
| Opus 5 | $0.00024 | $0.00958 |
| Sonnet 5 | $0.00010 | $0.00383 |
| Haiku 4.5 | $0.00005 | $0.00192 |
Grade A, and why
chip-seq-signal-pileup-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 12d 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 — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ChIP-Seq Signal Pileup Extension
Summary
Extend aligned ChIP-Seq reads to their predicted fragment length and generate genome-wide coverage (pileup) tracks. This is a critical intermediate step in peak calling that converts single-end or paired-end reads into continuous signal intensity maps needed for subsequent statistical comparison against background.
When to use
After duplicate filtering and fragment length prediction (d) in ChIP-Seq analysis, when you need to convert discrete read alignments into continuous coverage signal for comparison against control background. Specifically, apply this skill when preparing ChIP pileup tracks before constructing local bias models or performing statistical testing with bdgcmp.
When NOT to use
- When input reads are already in bedgraph or BigWig format (already represent continuous signal, not discrete alignments).
- When analyzing broad histone marks without prior fragment length prediction; use bdgbroadcall instead of narrow peak calling workflow.
- When fragment length d is unknown or invalid (negative, zero, or larger than biological expectation); predictd must succeed first.
Inputs
- Filtered ChIP-Seq BED file (duplicate-filtered reads with columns: chromosome, start, end, name, score, strand)
- Filtered control BED file (duplicate-filtered reads in BED format, optional but recommended)
- Predicted fragment length d in base pairs (integer, e.g. 254)
- Genome size (string code like 'hs' for human, or integer)
Outputs
- ChIP pileup bedgraph file (chromosome, start, end, coverage depth)
- Control pileup bedgraph file (chromosome, start, end, coverage depth)
- d-background bedgraph (control extended to d/2 bp, used for local bias at fragment scale)
- slocal-background bedgraph (control coverage in 1 kb window, used for local bias)
- llocal-background bedgraph (control coverage in 10 kb window, used for local bias)
How to apply
Use macs3 pileup on the filtered ChIP BED file with --extsize set to the predicted fragment length d (e.g., 254 bp for CTCF). This extends each aligned read in both directions to simulate the actual DNA fragment size, creating a bedgraph file where each genomic position is assigned a read count representing local sequencing depth. The extension parameter is critical because it normalizes for the fragment length that was determined in the predictd step, allowing proper comparison with control signal that is similarly extended. Generate separate pileup tracks for both ChIP and control samples; for control, additionally apply the -B flag to generate bidirectional background tracks at multiple scales (d/2, 1 kb, 10 kb) used in local bias calculation. The output bedgraph format preserves base-pair resolution coverage for downstream statistical testing.
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.
- 12d ago First seen · 103 lines · 48 tokens per session scan A 57c1229840fd
chip-seq-signal-pileup-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 48 tokens to every session and 1,916 once invoked, about $0.0002 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
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…