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 module-import-and-api-verificationgit 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/module-import-and-api-verification)<a href="https://agentmods.dev/skills/holobiomicslab/asb-skill-collections/module-import-and-api-verification"><img src="https://agentmods.dev/badge/skills/holobiomicslab/asb-skill-collections/module-import-and-api-verification/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/module-import-and-api-verification"><img src="https://agentmods.dev/badge/skills/holobiomicslab/asb-skill-collections/module-import-and-api-verification.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.00035 | $0.01529 |
| Opus 5 | $0.00017 | $0.00764 |
| Sonnet 5 | $0.00007 | $0.00306 |
| Haiku 4.5 | $0.00003 | $0.00153 |
Grade A, and why
module-import-and-api-verification 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 — 105 lines — stays where its author put it; the contents beside it link to each section on GitHub.
module-import-and-api-verification
Summary
Validate that required Python modules (e.g., iced for Hi-C ICE normalization) are correctly installed, importable, and expose the expected API before downstream pipeline steps depend on them. This skill detects installation failures, version mismatches, and missing transitive dependencies early.
When to use
Before invoking any Python module in a multi-step Hi-C processing pipeline, or when a dependency has been freshly installed or reinstalled. Specifically required in HiC-Pro when iced is needed for iterative correction and normalization of Hi-C contact matrices, since iced is no longer bundled with HiC-Pro source code and must be independently installed.
When NOT to use
- Module is already known to be installed and verified in a frozen, containerized environment (Docker, Singularity) where dependencies are immutable.
- Performing only static code analysis or linting that does not require runtime import.
- Installing dependencies for the first time — use standard package manager installation (pip install, conda install) as the primary step before verification.
Inputs
- Python interpreter (>3.7) with PATH to installation directory
- Module name (string) to import
- Optional: expected version string or API function name to probe
Outputs
- Boolean or exit code indicating successful import and API availability
- Version string of successfully imported module
- Configuration file documenting module path and PYTHONPATH for downstream steps
How to apply
After installing the target module (e.g., iced) and its transitive dependencies (numpy ≥1.18.1, scipy ≥1.4.1) via pip or setup.py, open a Python interpreter within the same environment and attempt to import the module by name. Check the module's version attribute or docstring to confirm it is present. Call a representative function or method from the module's public API (e.g., iced's normalization functions) to verify that the API surface is accessible and not corrupted. Document the import path, version, and any environment variables (e.g., PYTHONPATH) in a configuration file for reproducibility across cluster nodes or container restarts. If import or API check fails, diagnose the root cause: missing transitive dependencies, version incompatibility, incorrect PYTHONPATH, or conflicting installed packages.
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 · 105 lines · 35 tokens per session scan A e856ed2a586e
module-import-and-api-verification is a skill published in the GitHub repository HolobiomicsLab/asb-skill-collections (15 stars, last pushed yesterday), licensed Apache-2.0. It adds 35 tokens to every session and 1,529 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…
gsva-analysis-and-visualization
Use this skill to run GSVA or ssGSEA pathway-level differential analysis from a bulk expression matrix and a sample group file, then generate a heatmap from the saved GSVA result object. Trigger keywords: GSVA, ssGSEA, pathway enrichment, KEGG pathway analysis, MSigDB. NOT for: gene-level differential expression…
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…