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 niuz257470-ctrl/natureskills --skill nature-datagit clone --depth 1 https://github.com/niuz257470-ctrl/natureskillsWrote 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/niuz257470-ctrl/natureskills/nature-data)<a href="https://agentmods.dev/skills/niuz257470-ctrl/natureskills/nature-data"><img src="https://agentmods.dev/badge/skills/niuz257470-ctrl/natureskills/nature-data/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/niuz257470-ctrl/natureskills/nature-data"><img src="https://agentmods.dev/badge/skills/niuz257470-ctrl/natureskills/nature-data.svg" alt="Reviewed on agentmods" width="80" 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.00090 | $0.01270 |
| Opus 5 | $0.00045 | $0.00635 |
| Sonnet 5 | $0.00018 | $0.00254 |
| Haiku 4.5 | $0.00009 | $0.00127 |
Grade A, and why
nature-data 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 9d 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.
This is a copy
100% identical to nature-data — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 118 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Nature Data Availability Skill
Use this skill to turn a manuscript's supporting data into a transparent, Nature-ready data availability package: statement text, repository plan, dataset citations, and missing-information flags.
The governing policy layer is Springer Nature / Nature Portfolio data policy. The implementation layer is FAIR data practice and DataCite-style citation metadata.
Chinese-user operating mode
When the user writes in Chinese, provides a Chinese manuscript note, or asks for "中文对应", "中英对照", "数据可用性声明", "数据获取声明", "原始数据", "数据存储库", or "受限数据":
- Accept Chinese input naturally, but draft the final submission-ready statement in English unless the user explicitly asks for Chinese only.
- Preserve a short Chinese explanation of unresolved decisions when it helps the author act.
- Translate intent, not wording. Chinese phrases such as "可向通讯作者索取" are usually too vague for Nature-style English unless the restriction and access process are specified.
- Convert Chinese repository/status descriptions into precise publication terms:
数据可用性声明->Data Availability;原始数据->raw data;处理后数据->processed data;源数据->source data;补充材料->Supplementary Information;受限数据->restricted data;合理请求->reasonable request, only with reason and review route. - Use
references/chinese-author-alignment.mdfor Chinese terminology, common CN-to-EN failure modes, and bilingual intake questions.
Default stance
- Treat the Data Availability statement as a link between the paper's claims and the evidence needed to inspect, reproduce, or reuse them.
- Do not invent DOIs, accession numbers, repository names, licences, embargo dates, ethics approvals, access committees, or data-use conditions.
- Prefer public, discipline-specific repositories. Use generalist or institutional repositories only when no suitable community repository exists.
- Describe both newly generated data and reused third-party data.
- If data cannot be openly shared, state why, who controls access, how requests are evaluated, and what metadata or representative data can still be public.
- Separate data, code, materials, and protocols unless the journal asks for a combined availability section.
- Keep this skill focused on availability and metadata. Do not rewrite methods, analyze statistics, or polish the manuscript unless the user asks for those tasks separately.
- Flag "available upon request" as weak unless there is a specific legal, ethical, commercial, or third-party restriction.
What ships with it
8 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.
- 9d ago First seen · 118 lines · 90 tokens per session scan A 16761a2d6aef
nature-data is a skill published in the GitHub repository niuz257470-ctrl/natureskills (60 stars, last pushed 4mo ago), licensed MIT. It adds 90 tokens to every session and 1,270 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to nature-data, differing in 0 lines, and is treated as a copy.
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…