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 agentmods add skills/tiangzlab/omicsclaw/consensus-interpretnpx skills add TianGzlab/OmicsClaw --skill consensus-interpretgit clone --depth 1 https://github.com/TianGzlab/OmicsClawWrote 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/tiangzlab/omicsclaw/consensus-interpret)<a href="https://agentmods.dev/skills/tiangzlab/omicsclaw/consensus-interpret"><img src="https://agentmods.dev/badge/skills/tiangzlab/omicsclaw/consensus-interpret.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 | $0.00074 | $0.02068 |
| Opus 5 | $0.00037 | $0.01034 |
| Sonnet 5 | $0.00015 | $0.00414 |
| Haiku 4.5 | $0.00007 | $0.00207 |
Grade A, and why
consensus-interpret 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 yesterday.
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 — 186 lines — stays where its author put it; the contents beside it link to each section on GitHub.
consensus-interpret
When to use
The user has just finished a verified typed consensus run
(consensus-domains or sc-consensus-clustering) and wants the next
manual step (read cross_method_nmi.csv → run spatial-de →
cross-reference markers → name cell types → decide downstream skill) done
automatically with falsifiable evidence binding every LLM claim.
This skill does NOT replace the typed run. It is a strictly downstream
consumer: it reads <typed_run_dir>/{plan.json, consensus_labels.tsv, member_scores.csv, cross_method_nmi.csv} plus the original adata, and
writes its output to a different directory under
analysis://interpreted/<typed_run_id>. The verified-vs-exploratory
boundary established by ADR 0010 is preserved.
Skip when:
- The typed run did not produce
consensus_labels.tsv(i.e.consensus-domainsexited non-zero — fix the typed run first). - You are looking for a generic
query → skilldispatcher; useorchestratorfor that (forward direction). - You want to refine the consensus itself based on LLM judgment; that is explicitly forbidden by §11.4 "LLM never participates in statistical merging" and would be rejected by this skill's T3 invariants.
Inputs & Outputs
Inputs
- Input kinds:
directory - File types:
.json
Outputs
interpreted_report.mdinterpreted_assignments.jsonde_per_cluster.csvcontradiction_regions.csvaudit.json
Flow
1. Preflight (T1 — fail-fast if any fail)
├─ Load plan.json from --input; assert schema_version + typed run integrity
├─ Locate adata at plan.json.input_path (or --adata override); check exists
├─ Load consensus_labels.tsv; assert observation column ⊆ adata.obs.index
├─ Resolve marker DB:
│ --markers <path> if given;
│ else bundled `data/markers/panglaodb_<tissue>.tsv` for --tissue;
│ else exit 5 (MarkerDBUnavailable)
└─ If LLM required and unreachable AND --no-llm not set → exit 6 (LLMUnavailable)
2. Per-cluster differential expression (deterministic, scanpy)
└─ scanpy.tl.rank_genes_groups(adata, groupby=consensus_<operator>, method='wilcoxon')
→ de_per_cluster.csv with top-K markers per cluster (K=20 default)
3. Marker → cell-type lookup (deterministic, pre-LLM)
└─ For each cluster, compute candidate cell types by ranking DB entries
whose gene appears in the cluster's top-K markers (weighted by db.weight × 1/de_rank).
4. LLM grounded interpretation (γ + β; one call per cluster + one synthesis call)
├─ Prompt template embeds (per cluster):
│ cluster_id, n_cells, top-K DE markers,
│ DB candidate cell types (ranked),
│ member_agreement summary, cross_method_nmi neighbors
├─ LLM must return JSON conforming to interpreted_assignments.json
│ schema; mandatory evidence.markers[] with non-empty
│ {gene, db_source, db_celltype}
└─ After all clusters: one synthesis call to produce next_steps[]
with mandatory evidence_refs[] (capped at top-3 by priority)
5. Invariant enforcement (T3 — fail-fast if violated)
├─ Every cluster.evidence.markers != [] → else exit 7
├─ Every next_steps[*].evidence_refs != [] → else exit 7
└─ Banner present and matches one of two allowed values → else exit 7
6. Coverage check (T2 — escalate to T1 if floor breached)
└─ interpretable_cluster_frac < --coverage-floor → exit 8
7. Artifact writes
├─ interpreted_report.md (banner enforced in format_interpreted_report)
├─ interpreted_assignments.json
├─ de_per_cluster.csv
├─ contradiction_regions.csv
└─ audit.json
What ships with it
32 files 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.
- _artifacts.py 2.9 KB runs code
- _candidates.py 3.3 KB runs code
- _de.py 4.3 KB runs code
- _errors.py 1.7 KB runs code
- _invariants.py 2.4 KB runs code
- _llm.py 12 KB runs code
- _marker_db.py 5.7 KB runs code
- _metrics.py 6.2 KB runs code
- _report.py 6.9 KB runs code
- _run_reader.py 7.2 KB runs code
- consensus_interpret.py 9.5 KB runs code
- data/markers/cellmarker_liver.tsv 1.9 KB
- data/markers/panglaodb_brain.tsv 1.9 KB
- data/markers/panglaodb_immune.tsv 1.8 KB
- data/markers/panglaodb_kidney.tsv 1.6 KB
- data/markers/README.md 3.6 KB
- IMPLEMENTATION_PLAN.md 11 KB
- prompts/annotate.tmpl 1.8 KB
- prompts/next_steps.tmpl 2.1 KB
- references/methodology.md 2.1 KB
- references/output_contract.md 2.6 KB
- references/parameters.md 377 B
- skill.yaml 1.4 KB
- tests/test_candidates.py 6.2 KB runs code
- tests/test_cli_smoke.py 11 KB runs code
- tests/test_evaluation_panel.py 8.9 KB runs code
- tests/test_inline_de.py 5.4 KB runs code
- tests/test_interpreted_invariants.py 6.1 KB runs code
- tests/test_llm.py 11 KB runs code
- tests/test_marker_db.py 5.6 KB runs code
- tests/test_report_writers.py 10 KB runs code
- tests/test_run_reader.py 9.3 KB runs code
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.
- yesterday First seen · 186 lines · 74 tokens per session scan A 7d2c4e8bdf24
consensus-interpret is a skill published in the GitHub repository TianGzlab/OmicsClaw (160 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 74 tokens to every session and 2,068 once invoked, about $0.0004 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
scanpy
Standard single-cell RNA-seq analysis pipeline. Use for QC, normalization, dimensionality reduction (PCA/UMAP/t-SNE), clustering, differential expression, and visualization. Best for exploratory scRNA-seq analysis with established workflows. For deep learning models use scvi-tools; for data format questions use…
cellxgene-census-query
Query CZ CELLxGENE Census (61M+ cells). Filter by cell type/tissue/disease, retrieve expression data, and integrate with scanpy/PyTorch for population-scale single-cell analysis. Use this skill when: (1) Querying single-cell expression data by cell type, tissue, or disease, (2) Exploring available single-cell datasets…
single-cell-scrna-seq-analysis-scanpy
Complete single-cell RNA-seq analysis workflow built on Scanpy and AnnData. Use this skill when: (1) Loading diverse single-cell data formats (10X, h5ad, CSV), (2) Performing quality control and filtering, (3) Normalization, dimensionality reduction, and clustering, (4) Marker gene identification and cell type…
single-cell-multi-omics-analysis-scvi
Probabilistic deep learning framework for single-cell multi-omics data analysis. Use this skill when: (1) Analyzing single-cell RNA-seq data with batch correction, (2) Integrating multi-modal data (CITE-seq, ATAC-seq, multi-omics), (3) Performing cell type annotation with scANVI, (4) Spatial transcriptomics…
differential-analysis
Find differentially expressed genes between conditions, regions, or cell types. Use when user wants to compare gene expression, find markers, or identify condition-specific changes. Triggers: "differential expression", "DEG", "marker genes", "compare conditions", "what genes differ", "find markers", "condition…
functional-analysis
Understand the biological meaning of gene sets through pathway and functional enrichment analysis. Use when user has gene lists (DEGs, markers, SVGs) and wants to know what pathways or functions they represent. Triggers: "pathway analysis", "enrichment", "GSEA", "GO terms", "what pathways", "biological function"…