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 thesecondfox/skill --skill bio-workflows-cnv-pipelinegit clone --depth 1 https://github.com/thesecondfox/skillWrote 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/thesecondfox/skill/bio-workflows-cnv-pipeline)<a href="https://agentmods.dev/skills/thesecondfox/skill/bio-workflows-cnv-pipeline"><img src="https://agentmods.dev/badge/skills/thesecondfox/skill/bio-workflows-cnv-pipeline.svg" alt="Measured on agentmods" height="20"></a>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.00047 | $0.02554 |
| Opus 5 | $0.00023 | $0.01277 |
| Sonnet 5 | $0.00009 | $0.00511 |
| Haiku 4.5 | $0.00005 | $0.00255 |
Grade A, and why
bio-workflows-cnv-pipeline 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 4d 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 — 317 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Version Compatibility
Reference examples tested with: CNVkit 0.9+, GATK 4.5+
Before using code patterns, verify installed versions match. If versions differ:
- CLI:
<tool> --versionthen<tool> --helpto confirm flags
If code throws ImportError, AttributeError, or TypeError, introspect the installed package and adapt the example to match the actual API rather than retrying.
CNV Pipeline
"Detect copy number variants from my sequencing data" → Orchestrate CNVkit coverage analysis, segmentation, calling, visualization, and annotation for exome or targeted sequencing panels.
Complete workflow for detecting copy number variants from exome or targeted sequencing data.
Workflow Overview
BAM files (tumor/normal or germline)
|
v
[1. Target Preparation] --> Create/access target BED
|
v
[2. Coverage Calculation] --> Read depth per target
|
v
[3. Reference Creation] --> Pool of normals
|
v
[4. CNV Calling] --------> Log2 ratios, segmentation
|
v
[5. Visualization] ------> Scatter plots, heatmaps
|
v
[6. Annotation] ---------> Gene-level CNVs
|
v
CNV calls with gene annotations
Primary Path: CNVkit
Step 1: Prepare Target Regions
# If using exome capture kit BED
cnvkit.py target capture_targets.bed \
--annotate refFlat.txt \
--split \
-o targets.bed
# Access regions (off-target for WGS-like sensitivity)
cnvkit.py access genome.fa \
-o access.bed
cnvkit.py antitarget targets.bed \
--access access.bed \
-o antitargets.bed
Step 2: Calculate Coverage
# For each sample
for bam in *.bam; do
sample=$(basename $bam .bam)
# Target coverage
cnvkit.py coverage $bam targets.bed \
-o coverage/${sample}.targetcoverage.cnn
# Antitarget coverage
cnvkit.py coverage $bam antitargets.bed \
-o coverage/${sample}.antitargetcoverage.cnn
done
Step 3: Create Reference (Pool of Normals)
# From normal samples
cnvkit.py reference \
coverage/normal*.targetcoverage.cnn \
coverage/normal*.antitargetcoverage.cnn \
--fasta genome.fa \
-o reference.cnn
# Or flat reference (no normals available)
cnvkit.py reference \
--fasta genome.fa \
--targets targets.bed \
--antitargets antitargets.bed \
-o flat_reference.cnn
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 4d ago First seen · 317 lines · 47 tokens per session scan A c124d2f2b8e2
bio-workflows-cnv-pipeline is a skill published in the GitHub repository thesecondfox/skill (3 stars, last pushed 5mo ago), licensed MIT. It adds 47 tokens to every session and 2,554 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
instrument-data-to-allotrope
Convert laboratory instrument output files (PDF, CSV, Excel, TXT) to Allotrope Simple Model (ASM) JSON format or flattened 2D CSV. Use this skill when scientists need to standardize instrument data for LIMS systems, data lakes, or downstream analysis. Supports auto-detection of instrument types. Outputs include full…
exploratory-data-analysis
Perform bounded, local exploratory analysis of explicitly supported scientific files. Use for redacted CSV/TSV/JSON profiles; optional NumPy, HDF5, FASTA/FASTQ, and basic image metadata inspection; missingness/leakage audits; outlier and transformation sensitivity; and rigorous EDA report scaffolds. Other domain…
matlab
Build, review, migrate, and safely plan MATLAB or GNU Octave numerical workflows, including arrays, tabular/time data, tests, projects, graphics, MAT files, and explicit Python interoperability.
phylogenetics
Build and analyze phylogenetic trees using MAFFT (multiple alignment), IQ-TREE 2 (maximum likelihood), and FastTree (fast NJ/ML). Visualize with ETE3 or FigTree. For evolutionary analysis, microbial genomics, viral phylodynamics, protein family analysis, and molecular clock studies.
research-engineer
An uncompromising Academic Research Engineer. Operates with absolute scientific rigor, objective criticism, and zero flair. Focuses on theoretical correctness, formal verification, and optimal implementation across any required technology.
mapping-to-snomed
Maps clinical concept spans extracted by OpenMed to SNOMED CT concepts through a USER-SUPPLIED terminology server (the user's own Ontoserver, Snowstorm, or UMLS/UTS), never a bundled vocabulary. Use when the user wants to code findings, disorders, procedures, body structures, or substances to SNOMED CT, run an ECL…