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 makefile-based-build-system-configurationgit 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/makefile-based-build-system-configuration)<a href="https://agentmods.dev/skills/holobiomicslab/asb-skill-collections/makefile-based-build-system-configuration"><img src="https://agentmods.dev/badge/skills/holobiomicslab/asb-skill-collections/makefile-based-build-system-configuration/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/makefile-based-build-system-configuration"><img src="https://agentmods.dev/badge/skills/holobiomicslab/asb-skill-collections/makefile-based-build-system-configuration.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.00068 | $0.01926 |
| Opus 5 | $0.00034 | $0.00963 |
| Sonnet 5 | $0.00014 | $0.00385 |
| Haiku 4.5 | $0.00007 | $0.00193 |
Grade A, and why
makefile-based-build-system-configuration 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 — 108 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Makefile-based build system configuration
Summary
Configure a pipeline's build system by editing a configuration file and running make install to detect, validate, and resolve dependencies (samtools, bowtie2, Python libraries) across heterogeneous systems. This skill ensures all required tools and their versions are correctly installed and recorded before executing the main workflow.
When to use
When deploying a complex bioinformatics pipeline (e.g., HiC-Pro) that depends on multiple external tools with version constraints (samtools ≥1.9, bowtie2, R packages, Python libraries) and you need to verify their availability and configure their paths before running the analysis. Apply this skill before attempting to run any downstream analysis stages.
When NOT to use
- Input tools are already packaged in a containerized environment (Docker, Singularity) where versions are pre-configured—use the container directly instead.
- The pipeline has been pre-compiled or pre-installed on a shared cluster with a module system (e.g., 'module load hicpro'); configuration is already applied.
- You are running a lightweight analysis that does not depend on multiple versioned external tools with complex interdependencies.
Inputs
- config-install.txt (text configuration file with tool path variables)
- System environment variables ($PATH, $PYTHONPATH, $R_LIBS)
- Tool binaries or source distributions available on the system
Outputs
- config-system.txt (generated configuration file with resolved tool paths and versions)
- Verified installation status of samtools (≥1.9), bowtie2, Python (>3.7) with libraries (pysam, bx-python, numpy, scipy), R (with ggplot2, RColorBrewer packages)
How to apply
Edit the config-install.txt file to specify the full path to each required tool binary (samtools, bowtie2, R, Python) or leave fields unset to allow automatic detection via the system PATH using the 'which' command. Execute 'make CONFIG_SYS=config-install.txt install' to trigger dependency checking and configuration validation, which tests version constraints (e.g., samtools ≥1.9), attempts automatic installation of missing tools if permitted, and generates a config-system.txt file recording all resolved tool paths. Verify the generated config-system.txt contains entries for all critical tools (samtools, bowtie2, Python interpreter, and required libraries) and confirms version requirements are satisfied before proceeding to the analysis workflow.
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 · 108 lines · 68 tokens per session scan A 2785f4843939
makefile-based-build-system-configuration is a skill published in the GitHub repository HolobiomicsLab/asb-skill-collections (15 stars, last pushed yesterday), licensed Apache-2.0. It adds 68 tokens to every session and 1,926 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
estimate-immune-score-analysis
Use this skill to compute ESTIMATE immune-related microenvironment scores from a bulk expression matrix, generate an ESTIMATE score heatmap, and optionally generate group-wise ESTIMATE score boxplots plus significance tables when a sample group file is supplied. Trigger keywords: ESTIMATE, immune score, stromal score…
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…
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…
roc-diagnostic-performance
Use when evaluating diagnostic biomarker performance from case-control expression data with logistic regression and ROC curves, exporting coefficient and AUC tables together with a ROC PDF. NOT for: survival analysis, time-to-event outcomes, multiclass classification, calibration curves, decision-curve analysis, or…
wgcna-analysis
Use when building a weighted gene co-expression network from a bulk expression matrix and a sample group file, filtering variable genes by MAD, identifying co-expression modules with WGCNA, correlating modules with traits, and exporting module-level plots and gene tables. NOT for single-cell RNA-seq, differential…