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 bigbio/sdrf-skills --skill sdrf-setupgit clone --depth 1 https://github.com/bigbio/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-setup)<a href="https://agentmods.dev/skills/bigbio/sdrf-skills/sdrf-setup"><img src="https://agentmods.dev/badge/skills/bigbio/sdrf-skills/sdrf-setup.svg" alt="Measured on agentmods" 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.00039 | $0.00960 |
| Opus 5 | $0.00019 | $0.00480 |
| Sonnet 5 | $0.00008 | $0.00192 |
| Haiku 4.5 | $0.00004 | $0.00096 |
Grade A, and why
sdrf-setup 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 2d 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 — 117 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SDRF Setup Workflow
You are guiding the user through installing SDRF skills dependencies. Follow these steps.
In Cursor: The user invokes this by asking "install SDRF dependencies" or similar (no /sdrf-skills:sdrf-setup slash command). Ensure environment.yml and requirements.txt exist at the workspace root; if not, suggest cloning the full sdrf-skills repo or copying those files.
Step 1: Detect Available Package Managers
Check which package managers are available (run these in the terminal or ask the user):
command -v conda && conda --version
command -v mamba && mamba --version
command -v uv && uv --version
command -v pip && pip --version
- Conda or mamba: Recommended — best for thermorawfileparser (Thermo .raw files) via bioconda
- Pip: Works for sdrf-pipelines and techsdrf; thermorawfileparser requires conda
- uv: Can install Python tools; same limitation as pip for thermorawfileparser
Step 2: Provide Installation Commands
Based on what's available, output the exact commands the user should run.
Option A — Conda (recommended)
# From the sdrf-skills project directory:
conda env create -f environment.yml
conda activate sdrf-skills
If using mamba (faster):
mamba env create -f environment.yml
conda activate sdrf-skills
Option B — Pip (venv)
# From the sdrf-skills project directory:
python -m venv .venv
source .venv/bin/activate # On Windows: .venv\Scripts\activate
pip install -r requirements.txt
Note: With pip, thermorawfileparser is not available (not on PyPI). For Thermo .raw files, use conda.
Option C — uv
uv venv .venv
source .venv/bin/activate
uv pip install -r requirements.txt
Step 3: Verify Installation
After the user runs the commands, ask them to verify:
parse_sdrf --version
techsdrf --version
If both succeed, setup is complete.
Step 4: Optional — Spec Submodule
If the user cloned without submodules or wants the latest spec:
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.
- 2d ago Changed 71424d3346e3
- 8d ago First seen · 117 lines · 39 tokens per session scan A cf0082f56055
sdrf-setup is a skill published in the GitHub repository bigbio/sdrf-skills (18 stars, last pushed 2d ago), licensed MIT. It adds 39 tokens to every session and 960 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
sf-metadata-parser
Use this skill whenever the user wants to parse, analyze, document, or export SAP SuccessFactors OData metadata ($metadata XML). Triggers include: any mention of 'metadata', '$metadata', 'OData entities', 'entity fields', 'SF metadata', 'SuccessFactors schema', 'data dictionary', or requests to understand, compare, or…
akf-trust-metadata
The AI native file format. EXIF for AI — stamps every file with trust scores, source provenance, and compliance metadata. Embeds into 20+ formats (DOCX, PDF, images, code). EU AI Act, SOX, HIPAA auditing.
openmetadata-pr-review
Reviews OpenMetadata and Collate pull requests as a maintainer deciding whether to merge. Use WHENEVER the user asks to review a pull request — any phrasing ("review this PR", "PR review", "can you review.
connector-review
Review an OpenMetadata connector against golden standards. Runs multi-agent analysis covering architecture, code quality, type safety, testing, and performance. When a PR number is given, automatically posts the quality summary to the PR description and a detailed review as a PR comment.
scaffold-connector
Build a new OpenMetadata connector from scratch — scaffold JSON Schema, Python boilerplate, and AI context using schema-first architecture with code generation across Python, Java, TypeScript, and auto-rendered UI forms.
test-enforcement
Use after implementing any feature or fix to ensure comprehensive test coverage. Enforces 90% line coverage in openmetadata-service, integration tests for all API endpoints in openmetadata-integration-tests, and Playwright E2E tests for UI changes.