Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add bigbio/sdrf-skills/plugin install sdrf-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/bigbio/sdrf-skills/sdrf-contribute)<a href="https://agentmods.dev/skills/bigbio/sdrf-skills/sdrf-contribute"><img src="https://agentmods.dev/badge/skills/bigbio/sdrf-skills/sdrf-contribute/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/bigbio/sdrf-skills/sdrf-contribute"><img src="https://agentmods.dev/badge/skills/bigbio/sdrf-skills/sdrf-contribute.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Agent Snooping · line 104 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
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.00045 | $0.02787 |
| Opus 5.5 | $0.00018 | $0.01115 |
| Sonnet 5.5 | $0.00009 | $0.00557 |
| Haiku 4.5 | $0.00005 | $0.00279 |
Grade A, and why
sdrf-contribute scanned grade A with 1 finding 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 yesterday.
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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -fsSL "$url" -o existing.sdrf.tsv How it starts
The opening of the file, as written. The whole thing — 257 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SDRF Contribution Workflow
Bundle paths.
spec/,tools/anddata/ship with this skill, not with your working directory. Resolve every such path below against the bundle root (SDRF_SKILLS_ROOT, elseCLAUDE_PLUGIN_ROOT, else your sdrf-skills checkout):${SDRF_SKILLS_ROOT:-${CLAUDE_PLUGIN_ROOT}}/spec/sdrf-proteomics/TERMS.tsv. The helpers are thesdrf-toolscommand (install notes:sdrf-annotate/references/setup.md; check withsdrf-tools doctor); noPYTHONPATHor bundle-root variable is needed to run them. Files the user is annotating stay relative to the working directory.
You are helping the user contribute an annotated SDRF file back to the community repository
(bigbio/sdrf-annotated-datasets). This is the final step after annotation, validation,
and review — closing the loop from "I annotated a dataset" to "the community can reuse it."
Step 1: Check Prerequisites
1.1 Verify the PXD accession
- A ProteomeXchange accession (PXD######) must be provided
- If not provided, ask the user for it
1.2 Verify the SDRF content
- The SDRF must be available as a file on disk or from a previous annotation step
- If the user just finished
/sdrf-skills:sdrf-annotate, the content is in the conversation - Ask the user to confirm the file path or provide the content
1.3 Check if this is a new annotation or an update
Check if the PXD already exists in the community repository
(bigbio/sdrf-annotated-datasets):
Look for: datasets/{PXD}/{PXD}.sdrf.tsv
You can check via the GitHub API without cloning:
gh api repos/bigbio/sdrf-annotated-datasets/contents/datasets/{PXD} \
--silent && echo "exists" || echo "new"
Classify at the level of the file you are about to write, not the directory.
A PXD folder may legitimately hold several SDRFs with descriptive suffixes
(PXD006430-tmt.sdrf.tsv + PXD006430-silac.sdrf.tsv), so an existing folder
does not mean you are replacing anything:
gh api repos/bigbio/sdrf-annotated-datasets/contents/datasets/{PXD} \
--jq '.[] | select(.name | endswith(".sdrf.tsv")) | .name' 2>/dev/null
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.
- yesterday Changed acebf8d6fff2
- 1mo ago Changed 9b87b0e72cc8
- 1mo ago Changed · +6 lines 25b2e0ef9409
- 1mo ago Changed · -1 tokens per session 4e31bacb4b7a
- 1mo ago First seen · 251 lines · 46 tokens per session scan A 670fc723dc4a
sdrf-contribute is a skill published in the GitHub repository bigbio/sdrf-skills (19 stars, last pushed yesterday), licensed MIT. It adds 45 tokens to every session and 2,787 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
datalad
Retrieves, versions, and publishes scientific datasets with DataLad and git-annex, and captures computational provenance with datalad run, rerun, and containers-run. Use when cloning or fetching data from OpenNeuro, DANDI, datasets.datalad.org, or any DataLad dataset; when a file in a dataset reads as a broken symlink…
pr-checklist
Use when opening or finalizing a GitHub PR for OpenMetadata. Walks through the repo PR template — self-review against REVIEW.md, linked issue, high-level design (for big PRs), unit/integration/Playwright tests + coverage, UI screen recording, and manual test steps — then drafts a fully-filled PR body and (optionally)…
config-loading-precedence
How Xberg resolves config: CLI and server/MCP precedence, file walk-up, inline JSON, overrides. Use when adding a setting or one does not take effect.
conventional-commit-message
Generate high-quality Conventional Commit messages for repositories using conventional-changelog-conventionalcommits.
xberg-release
Xberg release on top of the shared release-workflow: task version:sync to bindings and chart, CI/Publish/Benchmarks readiness. Use before a release.
feature-workflow
Taking a multi-PR feature from "shape unknown" to merged without five review rounds per PR: spike until interfaces stop moving, write the contract, cut PRs along contract seams, one review per PR. Use when starting a feature that touches more than one lifecycle object or public interface, when a PR review keeps…