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/nvlabs/aspire/evosearchnpx skills add NVlabs/ASPIRE --skill evosearchgit clone --depth 1 https://github.com/NVlabs/ASPIREWrote 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/nvlabs/aspire/evosearch)<a href="https://agentmods.dev/skills/nvlabs/aspire/evosearch"><img src="https://agentmods.dev/badge/skills/nvlabs/aspire/evosearch.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.00037 | $0.00372 |
| Opus 5 | $0.00018 | $0.00186 |
| Sonnet 5 | $0.00007 | $0.00074 |
| Haiku 4.5 | $0.00004 | $0.00037 |
Grade A, and why
libero-evosearch 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 6d 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.
What it actually says
LIBERO Fix Loop + Evolutionary Search
Use this skill for Experiment 2. Start with INSTRUCTIONS.md.
Run Order
- Start with INSTRUCTIONS.md.
- Confirm the Fix Loop experiment has produced
fix_code.pyfor the target tasks. - Follow main-agent-prompt.md as the coordinator.
- Fill subagent-prompt.md once per task below the success threshold and dispatch subagents on the available worker GPUs.
- Read experiment-specific companion skills under skills/ when generating candidates.
- Use clean-task-slate.md before rerunning a task or suite.
Files
| File | Purpose |
|---|---|
| INSTRUCTIONS.md | End-to-end human/agent entrypoint |
| main-agent-prompt.md | Coordinator runbook for Evolutionary Search task dispatch and result collection |
| subagent-prompt.md | Per-task Evolutionary Search iteration prompt |
| clean-task-slate.md | Reset checklist before reruns |
| skills/evosearch-iteration.md | Candidate/eval/keyframe iteration mechanics |
| ../api-reference.md | LIBERO reduced API reference |
| ../skills/ | Shared LIBERO robot skills |
What ships with it
9 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.
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.
- 6d ago First seen · 30 lines · 37 tokens per session scan A 5357f33e771e
libero-evosearch is a skill published in the GitHub repository NVlabs/ASPIRE (127 stars, last pushed 5d ago), licensed Apache-2.0. It adds 37 tokens to every session and 372 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-30.
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…
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.
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…
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…