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 narrow-peak-coordinate-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/narrow-peak-coordinate-validation)<a href="https://agentmods.dev/skills/holobiomicslab/asb-skill-collections/narrow-peak-coordinate-validation"><img src="https://agentmods.dev/badge/skills/holobiomicslab/asb-skill-collections/narrow-peak-coordinate-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/narrow-peak-coordinate-validation"><img src="https://agentmods.dev/badge/skills/holobiomicslab/asb-skill-collections/narrow-peak-coordinate-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.00050 | $0.01391 |
| Opus 5 | $0.00025 | $0.00696 |
| Sonnet 5 | $0.00010 | $0.00278 |
| Haiku 4.5 | $0.00005 | $0.00139 |
Grade A, and why
narrow-peak-coordinate-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 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 — 96 lines — stays where its author put it; the contents beside it link to each section on GitHub.
narrow-peak-coordinate-validation
Summary
Verify that MACS3 callpeak correctly generates narrowPeak output files with valid peak coordinates and summit positions after processing paired-end ChIP-Seq data. This skill ensures the geometric correctness and completeness of peak call results before downstream analysis.
When to use
After running macs3 callpeak with the -f BEDPE flag on paired-end ChIP-Seq data (e.g., CTCF_PE_ChIP_chr22_50k.bedpe.gz), use this skill to validate that the narrowPeak output file exists and contains properly formatted peak coordinates and summit positions that align with the input fragment length estimates.
When NOT to use
- Input is already validated narrowPeak output from a trusted prior run; re-validation adds no new information.
- Single-end ChIP-Seq data where paired-end fragment length estimation is not applicable.
- Broad peak calling mode (bdgbroadcall) instead of narrow peak mode; validation logic for peak width assumptions differs.
Inputs
- narrowPeak file generated by macs3 callpeak
- macs3 predictd fragment length estimate (e.g., ~253 bp)
- Original paired-end bedpe input file metadata
Outputs
- Validated narrowPeak coordinate set
- Verification report of peak boundary correctness
- Summit position validity confirmation
How to apply
Inspect the narrowPeak output file generated by macs3 callpeak to confirm three criteria: (1) the file is present and non-empty; (2) each peak record contains valid BED coordinates (chromosome, start, end) with start < end and within expected genomic ranges; (3) summit positions are recorded and fall within the peak interval boundaries. Cross-check that peak coordinates align with the fragment length estimate (e.g., ~253 bp for the CTCF tutorial) by verifying that peak widths and spacing are consistent with the estimated insertion length reported by macs3 predictd. This validation confirms that paired-end mode extension was correctly applied during pileup and peak calling without requiring manual --extsize specification.
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 · 96 lines · 50 tokens per session scan A 231b224f9719
narrow-peak-coordinate-validation is a skill published in the GitHub repository HolobiomicsLab/asb-skill-collections (15 stars, last pushed yesterday), licensed Apache-2.0. It adds 50 tokens to every session and 1,391 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-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…