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 agentmods add skills/scitex-ai/scitex-python/_skillsnpx skills add scitex-ai/scitex-python --skill _skillsgit clone --depth 1 https://github.com/scitex-ai/scitex-pythonWhat 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 | $0.00033 | $0.00379 |
| Opus 5 | $0.00016 | $0.00189 |
| Sonnet 5 | $0.00007 | $0.00076 |
| Haiku 4.5 | $0.00003 | $0.00038 |
Grade A, and why
stx.cli 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.
The source is not reproduced here
Licensed AGPL-3.0
The repository is licensed AGPL-3.0, which this catalogue does not treat as permission to reproduce the file. Read it at the source.
What ships with it
4 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.
- 2d ago First seen · 45 lines · 33 tokens per session scan A d33191436d0a
stx.cli is a skill published in the GitHub repository scitex-ai/scitex-python (85 stars, last pushed 3d ago), licensed AGPL-3.0. It adds 33 tokens to every session and 379 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
design-lab
Scope the physical and interface design of a laboratory before configuring it. Use when a user asks how to approach a lab buildout, how to break a cell into components, which mechanism or instrument to choose, how to tailor a reference design to their material system or hazards, whether a design is over-engineered, or…
start-here
Establish or resume an OpenSDL laboratory through a normal agent conversation. Use when a user says start here, set up or configure my lab, plan a new lab or cell, describe existing equipment, continue a lab build, or turn a laboratory idea into a simulator-first implementation plan.
develop-workflow
Design, change, validate, and test an OpenSDL workflow through a simulation manifest. Use when building or iterating on a laboratory workflow without live equipment.
orient-lab
Inspect the current OpenSDL repository and declared laboratory state. Use when a user asks for current status or needs a declared-state baseline before a concrete task; use start-here for setup planning, inventory changes, or new equipment.
release
Build and validate OpenSDL release candidates by synchronizing versions and producing every workspace distribution locally. Use when cutting or rehearsing a coordinated project release. It does not publish, sign, or tag.
author-skill
Create, revise, split, or remove an OpenSDL repository skill. Use when a recurring agent procedure needs portable triggers, instructions, resources, validation, and fresh-session tests.