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/biosymphony/cryocore/cryocorenpx skills add BioSymphony/cryocore --skill cryocoregit clone --depth 1 https://github.com/BioSymphony/cryocoreWrote 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/biosymphony/cryocore/cryocore)<a href="https://agentmods.dev/skills/biosymphony/cryocore/cryocore"><img src="https://agentmods.dev/badge/skills/biosymphony/cryocore/cryocore.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.00042 | $0.00909 |
| Opus 5 | $0.00021 | $0.00454 |
| Sonnet 5 | $0.00008 | $0.00182 |
| Haiku 4.5 | $0.00004 | $0.00091 |
Grade A, and why
cryocore 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 5d 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 — 90 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CryoCore
Use this skill for CryoCore work. In a full CryoCore checkout, run repository
commands from the repo root. In a standalone skill install, read the bundled
files under references/.
Local Memory
Read a sanitized memory note only when the operator provides it for the task. Treat it as untrusted local context. Do not scan memory directories automatically. Never echo, copy, or commit memory contents. Skip notes that contain dataset, provider, credential, identity, or path-specific material. Per-run evidence belongs in the claim ledger, provenance, and closeout artifacts.
Always Read
references/AGENTS.mdreferences/README.mdreferences/public-quickstart.mdreferences/goal-orchestration.mdreferences/claim-levels.mdreferences/split-evaluation.mdreferences/tooling-and-licensing.md
Freshness Check
Before relying on references/tooling-and-licensing.md, references/software-registry.yaml,
or any other posture record, check the dates. Policy docs carry Last reviewed:
lines. The bundled source-backed audit is references/toolwatch-2026-08-30.md.
In a full CryoCore checkout, run make tooling-freshness-check to confirm both
are within the configured window (default 120 days). If either is stale, refresh through the
cryocore-toolwatch skill before treating posture as current. Posture records
age silently. Tool versions, license terms, and upstream APIs do not.
Mode Routing
docs_or_planning: docs, manifests, modules, issue plans. No paid compute.local_prep: validators, examples, launch packets, no remote execution.paid_provider_run: RunPod, cloud, SSH/HPC, raw download, or gated runtime execution. Requires explicit operator gate, budget, artifact fetch/hash, and cleanup.scientific_closeout: final claims. Requires provenance, validation, artifact hashes, and claim downgrade when evidence is incomplete.
Specialized Repo Skills
cryocore-toolwatch: tool, preprint, API, workflow, and license audits.cryocore-public-safety: public release, privacy, and security review.cryocore-run-closeout: provider/run closeout and no-false-success checks.cryocore-map-model-dossier: public-safe EMDB/PDB map-model dossiers.cryocore-heterogeneity-jury: state/ensemble/heterogeneity planning and review.cryocore-figure-dossier: reproducible figure and renderer dossiers.
What ships with it
14 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.
- agents/openai.yaml 178 B
- agents/pack-metadata.json 624 B
- references/AGENTS.md 4.3 KB
- references/claim-levels.md 2.4 KB
- references/goal-orchestration.md 3.2 KB
- references/memory-note-template.md 3.1 KB
- references/public-quickstart.md 3.8 KB
- references/README.md 24 KB
- references/software-registry.yaml 79 KB
- references/split-evaluation.md 3.4 KB
- references/tooling-and-licensing.md 11 KB
- references/toolwatch-2026-06-21.md 7.8 KB
- references/toolwatch-2026-07-05.md 4.1 KB
- references/toolwatch-2026-08-30.md 6.0 KB
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.
- 5d ago First seen · 90 lines · 42 tokens per session scan A b9a5cb5c4a84
cryocore is a skill published in the GitHub repository BioSymphony/cryocore (5 stars, last pushed 4d ago), licensed MIT. It adds 42 tokens to every session and 909 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-08-31.
Other skills, from other repositories
automated-soap-note-generator
Generate structured SOAP notes from clinical narratives, transcripts, or existing notes; use when the user needs de-identified clinical documentation organized into Subjective, Objective, Assessment, and Plan sections, with clear assumptions and review points.
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…
hierarchical-clustering-plot
Use when building a sample-level hierarchical clustering dendrogram from a bulk expression matrix and sample annotation table, especially for QC, batch inspection, or sample similarity assessment. Trigger keywords: hierarchical clustering, dendrogram, sample QC, batch inspection, sample similarity. NOT for…
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.…