synthetic-sciences/openscience is an AI workbench that carries out scientific research by reading papers, forming hypotheses, writing and running code, conducting experiments, analyzing results, and preparing reports. Researchers use it for work in machine learning, biology, physics, and chemistry with remote or local models. Catalogue add-ons extend its scientific workflows through skills and instructions.
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 synthetic-sciences/openscience --skill protocolsio-integrationgit clone --depth 1 https://github.com/synthetic-sciences/openscienceWrote 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/synthetic-sciences/openscience/protocolsio-integration)<a href="https://agentmods.dev/skills/synthetic-sciences/openscience/protocolsio-integration"><img src="https://agentmods.dev/badge/skills/synthetic-sciences/openscience/protocolsio-integration/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/synthetic-sciences/openscience/protocolsio-integration"><img src="https://agentmods.dev/badge/skills/synthetic-sciences/openscience/protocolsio-integration.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 7 findings, up to high
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 →
- high Privilege Escalation · line 37 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
- high Privilege Escalation · line 41 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
- high Privilege Escalation · line 125 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
- high Privilege Escalation · line 200 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
- medium Data Exfiltration · line 293 Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
- medium Data Exfiltration · line 320 Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
- medium Data Exfiltration · line 293 Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
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.00085 | $0.03209 |
| Opus 5.5 | $0.00034 | $0.01284 |
| Sonnet 5.5 | $0.00017 | $0.00642 |
| Haiku 4.5 | $0.00009 | $0.00321 |
Grade B, and why
protocolsio-integration scanned grade B with 2 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 1mo 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.
Sends data to an external URLmediumData exfiltration
A POST to an outside endpoint may be telemetry or may be exfiltration; either way the mod talks to somewhere, and you should know where.
response = requests.post( "https://protocols.io/api/v3/protocols", Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
response = requests.get( Copies of this mod
8 near-identical copies found in the catalogue:
- protocolsio-integration — 100% identical, 10 lines differ
- protocolsio-integration — 100% identical, 9 lines differ
- protocolsio-integration — 100% identical, 9 lines differ
- protocolsio-integration — 100% identical, 10 lines differ
- protocolsio-integration — 100% identical, 10 lines differ
- protocolsio-integration — 100% identical, 11 lines differ
- protocolsio-integration — 100% identical, 7 lines differ
- protocolsio-integration — 95% identical, 10 lines differ
How it starts
The opening of the file, as written. The whole thing — 427 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Protocols.io Integration
Overview
Protocols.io is a comprehensive platform for developing, sharing, and managing scientific protocols. This skill provides complete integration with the protocols.io API v3, enabling programmatic access to protocols, workspaces, discussions, file management, and collaboration features.
When to Use This Skill
Use this skill when working with protocols.io in any of the following scenarios:
- Protocol Discovery: Searching for existing protocols by keywords, DOI, or category
- Protocol Management: Creating, updating, or publishing scientific protocols
- Step Management: Adding, editing, or organizing protocol steps and procedures
- Collaborative Development: Working with team members on shared protocols
- Workspace Organization: Managing lab or institutional protocol repositories
- Discussion & Feedback: Adding or responding to protocol comments
- File Management: Uploading data files, images, or documents to protocols
- Experiment Tracking: Documenting protocol executions and results
- Data Export: Backing up or migrating protocol collections
- Integration Projects: Building tools that interact with protocols.io
Core Capabilities
This skill provides comprehensive guidance across five major capability areas:
1. Authentication & Access
Manage API authentication using access tokens and OAuth flows. Includes both client access tokens (for personal content) and OAuth tokens (for multi-user applications).
Key operations:
- Generate authorization links for OAuth flow
- Exchange authorization codes for access tokens
- Refresh expired tokens
- Manage rate limits and permissions
Reference: Read references/authentication.md for detailed authentication procedures, OAuth implementation, and security best practices.
2. Protocol Operations
Complete protocol lifecycle management from creation to publication.
Key operations:
- Search and discover protocols by keywords, filters, or DOI
- Retrieve detailed protocol information with all steps
- Create new protocols with metadata and tags
- Update protocol information and settings
- Manage protocol steps (create, update, delete, reorder)
- Handle protocol materials and reagents
- Publish protocols with DOI issuance
- Bookmark protocols for quick access
- Generate protocol PDFs
What ships with it
6 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.
- 1mo ago Changed · +6 lines 1d64e4e732e8
- 1mo ago First seen · 421 lines · 85 tokens per session scan B 899f0e2886c2
protocolsio-integration is a skill published in the GitHub repository synthetic-sciences/openscience (4,025 stars, last pushed yesterday), licensed Apache-2.0. It adds 85 tokens to every session and 3,209 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it B with 2 findings (sends data to an external url, 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
knowledge-shared-api-and-runtime-schemas
Shared request and response definitions for the server and web app, with runtime checks for incoming data and cleaned JSON schemas for tools. TypeBox is the library used to describe these data shapes.
knowledge-interaction-surfaces-cli-bootstrap-headless-and-print
A codebase guide for the command-line startup path, including interactive, non-interactive, print, and structured JSONL output modes.
knowledge-interaction-surfaces-hono-server-api-and-streaming
A codebase guide for the server API that connects web clients and automation tools to sessions, tasks, live event streams, terminals, and browser runtimes.
knowledge-model-and-provider-runtime
A codebase guide for choosing AI models and providers, sending requests, recovering from failures, and recording runtime information.
knowledge-tool-contracts-and-registry
A common contract and registry for built-in tools, MCP tools, and agent-facing tools. It validates tool parameters, decides which tools are visible to a model, and stores session artifacts privately.
songsee
Audio spectrograms/features (mel, chroma, MFCC) via CLI.