science-data-code

science-data-code is a skill for Claude Code, Codex from shikaijieskj/science-skills. It costs 93 tokens per session (574 once invoked), scanned A, original, MIT.

A skill for preparing and checking statements about research data, code, materials, repositories, and reproducibility for Science-family journals. Reproducibility means giving others enough information or resources to inspect and repeat the work.

In plain words
What is it for?
Use it to draft data-availability, code-availability, and materials-availability statements, plan repository deposits, map source data, or check FAIR metadata, meaning that research resources are findable, accessible, interoperable, and reusable.
Why use it?
It helps connect each manuscript claim with the data, code, materials, and metadata needed to verify it. It also flags weak access plans and avoids inventing repository identifiers, licenses, or availability details.

Skill for Claude CodeCodex

Written for Claude Code and Codex: shipped in a Claude Code plugin, but also agents/openai.yaml present.

Part of the science-skills plugin — 9 skills shipped together

Good fit Use it to draft data-availability, code-availability, and materials-availability statements, plan repository deposits, map source data, or check FAIR metadata, meaning that research resources are findable, accessible, interoperable, and reusable.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/shikaijieskj/science-skills/science-data-code
Install

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.

Any agent
npx skills add shikaijieskj/science-skills --skill science-data-code
Clone the repo
git clone --depth 1 https://github.com/shikaijieskj/science-skills

Made for: Claude Code, Codex.

Or install science-skills, the plugin that ships this one along with the rest of its 9 skills.

Wrote 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.

agentmods badge for science-data-code

README.md
[![agentmods](https://agentmods.dev/badge/skills/shikaijieskj/science-skills/science-data-code/github.svg)](https://agentmods.dev/skills/shikaijieskj/science-skills/science-data-code)
Your own site
<a href="https://agentmods.dev/skills/shikaijieskj/science-skills/science-data-code"><img src="https://agentmods.dev/badge/skills/shikaijieskj/science-skills/science-data-code/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.

agentmods 80×15 button for science-data-code

Your own site · 80×15
<a href="https://agentmods.dev/skills/shikaijieskj/science-skills/science-data-code"><img src="https://agentmods.dev/badge/skills/shikaijieskj/science-skills/science-data-code.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 93 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 574 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00093 $0.00574
Opus 5 $0.00046 $0.00287
Sonnet 5 $0.00019 $0.00115
Haiku 4.5 $0.00009 $0.00057

Measured 10d ago against content hash c52ef4e30915, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

science-data-code 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 10d 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.

skills/science-data-code/SKILL.md · 62 lines

How it starts

The opening of the file, as written. The whole thing — 62 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Science Data and Code

Use this skill to connect the manuscript's claims to inspectable data, code, materials, and metadata. Treat availability as part of the evidence chain.

Default stance

  • Do not invent DOIs, accession numbers, repository records, licenses, embargoes, ethics approvals, access committees, or code status.
  • Prefer public, stable, discipline-appropriate repositories.
  • Separate data, code, materials, protocols, models, and third-party resources.
  • Flag available upon reasonable request as weak unless there is a clear legal, ethical, commercial, privacy, or third-party restriction.
  • Verify current target-journal policy before final submission wording.

Open extra files

File Open when
references/availability-patterns.md Need ready-to-adapt data/code/materials statement patterns
references/repository-checklist.md Need repository, identifier, license, metadata, or FAIR checks
references/source-basis.md Need source hierarchy or policy-vs-advice boundaries

Workflow

  1. Identify target journal and article type.
  2. Inventory every asset needed to support the main and supplementary claims: raw data, processed data, figure source data, code, scripts, models, protocols, materials, third-party datasets, and restricted data.
  3. Map each asset to one access route: public repository, controlled access, within paper/supplement, reused public source, third-party restricted, available on justified request, or not yet provided.
  4. Choose a repository and identifier strategy before drafting.
  5. Draft data/code/materials availability text with asset-to-location mapping.
  6. Add missing-information flags.
  7. Run the FAIR/reproducibility checklist.

Output format

Data and code availability
[ready-to-paste statement]

Asset map
| Asset | Supports claim/figure | Location | Identifier | Access conditions | Missing info |

Repository actions
- [specific actions]

Risk flags
- [specific flags or "None"]

Read the full file on GitHub · 62 lines

Files

What ships with it

4 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.

Changes

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.

  1. 10d ago First seen · 62 lines · 93 tokens per session scan A c52ef4e30915

Subscribe to this mod's changes

science-data-code is a skill published in the GitHub repository shikaijieskj/science-skills (5 stars, last pushed 3mo ago), licensed MIT. It adds 93 tokens to every session and 574 once invoked, about $0.0005 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.

Related

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…

anthropics/knowledge-work-plugins · 123 tokens

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.

K-Dense-AI/scientific-agent-skills · 42 tokens

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…

K-Dense-AI/scientific-agent-skills · 83 tokens

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.

K-Dense-AI/scientific-agent-skills · 68 tokens

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.

davila7/claude-code-templates · 43 tokens

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…

maziyarpanahi/openmed · 205 tokens