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 Boom5426/Nature-Paper-Skills --skill data-availabilitygit clone --depth 1 https://github.com/Boom5426/Nature-Paper-SkillsWrote 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/boom5426/nature-paper-skills/data-availability)<a href="https://agentmods.dev/skills/boom5426/nature-paper-skills/data-availability"><img src="https://agentmods.dev/badge/skills/boom5426/nature-paper-skills/data-availability/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/boom5426/nature-paper-skills/data-availability"><img src="https://agentmods.dev/badge/skills/boom5426/nature-paper-skills/data-availability.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00040 | $0.00750 |
| Opus 5 | $0.00020 | $0.00375 |
| Sonnet 5 | $0.00008 | $0.00150 |
| Haiku 4.5 | $0.00004 | $0.00075 |
Grade A, and why
data-availability 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.
How it starts
The opening of the file, as written. The whole thing — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Data Availability
Overview
Use this skill to turn manuscript-supporting data into a submission-ready availability package: statement text, repository plan, source-data mapping, and unresolved-risk flags.
This skill is narrower than submission-audit and more operational than scientific-writing. Use it when the bottleneck is no longer the paper's story, but whether the data-sharing package is specific, durable, and journal-ready.
When To Use
Use this skill when:
- the manuscript needs a
Data Availabilitystatement - accession numbers, DOIs, repository records, or source-data files are missing or unstable
- the paper mixes generated data, reused public data, and restricted data
- "available upon request" wording needs to be tightened or replaced
- a submission or revision needs data-sharing text that editors can audit quickly
Do not use this skill for:
- generic section rewriting unrelated to data sharing
- full manuscript restructuring
- bibliography cleanup that does not affect dataset availability
Workflow
- Identify the target journal and article type.
- Inventory the datasets that support the main and supplementary claims:
- raw data
- processed data
- figure source data
- reused public datasets
- code-adjacent outputs that are necessary to inspect the results
- Assign each dataset one access route only:
- public repository
- controlled-access repository
- within paper or supplement
- reused public source
- third-party restricted
- justified request route
- Choose repository and identifier strategy before drafting the statement.
- Draft explicit dataset-to-location wording.
- Check that the statement covers both newly generated and reused data.
- Flag unresolved fields rather than inventing repository names, accession IDs, DOIs, or access rules.
Working Rules
- Prefer public, discipline-specific repositories when possible.
- Treat
available upon requestas weak unless a real legal, ethical, commercial, or third-party restriction exists. - If data cannot be public, state:
- why access is restricted
- who controls access
- how requests are reviewed
- what metadata, source data, or derived data remain public
- Do not merge data, code, protocols, and materials into one vague availability sentence unless the journal explicitly wants that.
- Do not invent accession numbers, DOIs, repository names, reviewer links, or embargo terms.
What ships with it
5 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.
- 10d ago First seen · 87 lines · 40 tokens per session scan A 172608ff68e8
data-availability is a skill published in the GitHub repository Boom5426/Nature-Paper-Skills (489 stars, last pushed 4d ago), licensed MIT. It adds 40 tokens to every session and 750 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…