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 methylation-probe-count-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/methylation-probe-count-validation)<a href="https://agentmods.dev/skills/holobiomicslab/asb-skill-collections/methylation-probe-count-validation"><img src="https://agentmods.dev/badge/skills/holobiomicslab/asb-skill-collections/methylation-probe-count-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/methylation-probe-count-validation"><img src="https://agentmods.dev/badge/skills/holobiomicslab/asb-skill-collections/methylation-probe-count-validation.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Anti-Refusal · line 80 Skill instructs the agent to omit warnings, disclaimers, or ethical commentary. Stripping safety caveats hides risk from the user and is a common jailbreak preamble.Fix: Remove instructions that suppress warnings, disclaimers, or ethical commentary. Let the agent surface safety-relevant caveats to the user.
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.00031 | $0.01244 |
| Opus 5 | $0.00015 | $0.00622 |
| Sonnet 5 | $0.00006 | $0.00249 |
| Haiku 4.5 | $0.00003 | $0.00124 |
Grade A, and why
methylation-probe-count-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.
methylation-probe-count-validation
Summary
Validate that DNA methylation array data has been loaded with the correct total number of probes before quality-based filtering. This skill confirms successful data import and array-type detection by verifying pre-filter probe counts against expected canonical values for HumanMethylation450K and EPIC arrays.
When to use
Apply this skill immediately after loading raw methylation array data using champ.load() or champ.import() to verify data integrity. Use it when you need confidence that the correct array type was detected and all available probes were successfully imported before any downstream filtering, normalization, or analysis steps.
When NOT to use
- Data has already been filtered by quality metrics; expected probe counts only apply to unfiltered raw imports.
- Array type is unknown or non-standard (e.g., mouse arrays or custom manifests); canonical probe counts apply only to human 450K and EPIC v1/v2.
- Input is a pre-processed feature table or reduced dataset; this skill requires raw array data at full probe dimensionality.
Inputs
- .idat files (methylation array raw data)
- beta-valued matrix
- array type specification (450K or EPIC)
- ChAMPdata annotation package (version ≥2.23.1)
Outputs
- pre-filter probe count integer
- confirmation of array type detection
- validated methylation data object ready for downstream analysis
How to apply
Load methylation array data from .idat files or a beta-valued matrix using champ.load() with the appropriate array type specification. Extract the pre-filter probe count from the returned data object before any quality-control or filtering steps are applied. Compare the reported probe count against the expected canonical values: 485,512 probes for HumanMethylation450 (450K) arrays and 867,531 probes for EPIC arrays. If the observed count matches the expected value, data import was successful and array-type detection is correct. If counts deviate, investigate array annotation mismatches or file corruption.
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 · 31 tokens per session scan A add076f8eebb
methylation-probe-count-validation is a skill published in the GitHub repository HolobiomicsLab/asb-skill-collections (15 stars, last pushed yesterday), licensed Apache-2.0. It adds 31 tokens to every session and 1,244 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-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…