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/datalab-atom/evoany/reportnpx skills add DataLab-atom/EvoAny --skill reportgit clone --depth 1 https://github.com/DataLab-atom/EvoAnyWrote 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/datalab-atom/evoany/report)<a href="https://agentmods.dev/skills/datalab-atom/evoany/report"><img src="https://agentmods.dev/badge/skills/datalab-atom/evoany/report.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.00005 | $0.00273 |
| Opus 5 | $0.00003 | $0.00137 |
| Sonnet 5 | $0.00001 | $0.00055 |
| Haiku 4.5 | $0.00001 | $0.00027 |
Grade A, and why
report 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 3d 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
/report — Evolution Report
- Call
evo_get_statusfor current state - For each target, call
evo_get_lineageon its best branch - Read
memory/global/long_term.mdfor accumulated insights - Read
memory/synergy/records.mdfor cross-function results exec git -C <repo> log --graph --oneline --allfor visual lineage
Generate a Markdown report:
## Evolution Summary
- Generations: {N}
- Total evaluations: {total_evals}
- Seed baseline: {seed_obj}
- Best overall: {best_obj_overall} ({improvement})
## Per-Target Results
| Target | Seed | Best | Improvement | Key Generation |
|--------|------|------|-------------|----------------|
| ... | ... | ... | ... | ... |
## Key Breakthroughs
- Gen {N}: {target} — {what changed} ({delta})
## Synergy Results
- {targetA} × {targetB}: {result}
## Lessons Learned
{from long_term memory}
## Failed Approaches
{from failures.md}
## Evolution Tree
{git log graph}
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.
- 3d ago First seen · 43 lines · 5 tokens per session scan A 3e6f3b6b90f6
report is a skill published in the GitHub repository DataLab-atom/EvoAny (37 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 5 tokens to every session and 273 once invoked, about $0.0000 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
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…
nature-statistics
Audit, revise, or draft manuscript statistical reporting for Nature / high-impact journal submissions. Use when the user asks to check statistical analysis sections, p values, confidence intervals, sample size, biological versus technical replicates, randomization, blinding, multiple-comparison correction, model…
evaluating-with-leakage-gates
Evaluate an OpenMed de-identification or clinical NER model against the leakage-first release gates G1a through G8, which gate releases on residual PHI leakage rather than on F1. Use when the user wants to run the OpenMed eval harness on a synthetic golden set, decide whether a de-id model is RELEASABLE or…
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…
mixed-precision
Use FP16/BF16 mixed precision to accelerate training and reduce memory. Use when optimizing GPU performance.
indication-dossier
Build a source-backed biomedical indication dossier. Use when a research task asks for disease biology, target rationale, patient segmentation, biomarkers, trials, drugs, competitive landscape, or translational evidence.