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 agentlas-ai/agentlas-desktop --skill labarchive-integrationgit clone --depth 1 https://github.com/agentlas-ai/agentlas-desktopWrote 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/agentlas-ai/agentlas-desktop/labarchive-integration)<a href="https://agentmods.dev/skills/agentlas-ai/agentlas-desktop/labarchive-integration"><img src="https://agentmods.dev/badge/skills/agentlas-ai/agentlas-desktop/labarchive-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/agentlas-ai/agentlas-desktop/labarchive-integration"><img src="https://agentmods.dev/badge/skills/agentlas-ai/agentlas-desktop/labarchive-integration.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00052 | $0.02339 |
| Opus 5.5 | $0.00021 | $0.00936 |
| Sonnet 5.5 | $0.00010 | $0.00468 |
| Haiku 4.5 | $0.00005 | $0.00234 |
Grade A, and why
labarchive-integration 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 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.
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.
This is a copy
100% identical to labarchive-integration — 45 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 234 lines — stays where its author put it; the contents beside it link to each section on GitHub.
LabArchives Integration
Use LabArchives APIs only from current, official method pages. The public documentation is a shared notebook, not a versioned SDK reference, so verify the specific page immediately before implementing a remote operation.
Choose the Correct Surface
Do not combine these interfaces:
- Legacy ELN API: notebook trees, entries, attachments, users, searches,
exports, and site-license functions. It uses regional
*api.labarchives.comhosts,/api/<class>/<method>paths, XML for many responses, and signed query parameters. - Inventory API v1: inventory, item types, orders, storage locations, and
vendors. It documents relative
/public/v1/...paths, JSON schemas, and signedX-LabArchives-*request headers. - Product integrations: Jupyter, REDCap, Protocols.io, GraphPad Prism, SnapGene, Geneious, and others are product-specific UI or file workflows. They are not evidence of a general LabArchives OAuth 2.0 API.
Read references/api_reference.md before writing
API code and references/integrations.md before
automating an advertised integration.
Access and Credentials
LabArchives ELN developer API access is an Enterprise capability. The current Inventory FAQ limits Inventory API access to Enterprise and Enterprise Plus licensees and requires an Inventory account with API permission. Contact the institution's LabArchives team or LabArchives support for access and the development documentation supplied with it.
The environment names below are conventions of this skill, not vendor-defined standards:
LABARCHIVES_ELN_API_URL— one exact regional ELN API URL ending in/apiLABARCHIVES_ACCESS_KEY_ID— LabArchives-issued Access Key ID (akid)LABARCHIVES_ACCESS_PASSWORD— HMAC signing secretLABARCHIVES_USER_ID— optional persistent UID bound to that Access Key IDLABARCHIVES_INVENTORY_LAB_ID— required for Inventory requests
Keep secrets in the process environment or an approved secret manager. Do not
put them in YAML, source code, command-line arguments, prompts, logs, notebooks,
or committed .env files. The bundled tools never search for .env files.
What ships with it
7 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 First seen · 234 lines · 52 tokens per session scan A 2dbe25bc14be
labarchive-integration is a skill published in the GitHub repository agentlas-ai/agentlas-desktop (6 stars, last pushed yesterday), licensed Apache-2.0. It adds 52 tokens to every session and 2,339 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to labarchive-integration, differing in 45 lines, and is treated as a copy.
Other skills, from other repositories
exporting-bulk-fhir
Kick off and harvest a FHIR Bulk Data $export (system-, group-, or patient-level) and stream the resulting NDJSON into a batch OpenMed de-identification + NER pipeline at cohort scale. Covers the async kickoff (Prefer respond-async) -> poll Content-Location -> download NDJSON flow, the Bulk Data Access IG, type/since…
fetching-fhir-resources
Fetches and pages FHIR R4 resources (Patient, DocumentReference, DiagnosticReport, Observation, Condition) from a FHIR REST server, decodes base64 attachments, and extracts clinical narrative for OpenMed. Use before OpenMed processing when pulling charts from an EHR FHIR API (Epic, Cerner/Oracle, HAPI, or any US Core…
devtu-create-tool
Create new scientific tools for ToolUniverse framework with proper structure, validation, and testing. Use when users need to add tools to ToolUniverse, implement new API integrations, create tool wrappers for scientific databases/services, expand ToolUniverse capabilities, or follow ToolUniverse contribution…
claude-api
Build, debug, and optimize Claude API / Anthropic SDK apps. Apps built with this skill should include prompt caching. Also handles migrating existing Claude API code between Claude model versions (4.5 → 4.6, 4.6 → 4.7, retired-model replacements). TRIGGER when: code imports anthropic/@anthropic-ai/sdk; user asks for…
vellum-oauth-integrations
Act on behalf of your user in any third-party software that supports OAuth 2.0.
protocolsio-integration
Integration with protocols.io API for managing scientific protocols. This skill should be used when working with protocols.io to search, create, update, or publish protocols; manage protocol steps and materials; handle discussions and comments; organize workspaces; upload and manage files; or integrate protocols.io…