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/fl-sean03/opensdl/start-herenpx skills add fl-sean03/OpenSDL --skill start-heregit clone --depth 1 https://github.com/fl-sean03/OpenSDLWrote 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/fl-sean03/opensdl/start-here)<a href="https://agentmods.dev/skills/fl-sean03/opensdl/start-here"><img src="https://agentmods.dev/badge/skills/fl-sean03/opensdl/start-here.svg" alt="Measured on agentmods" 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 | $0.00061 | $0.00786 |
| Opus 5 | $0.00030 | $0.00393 |
| Sonnet 5 | $0.00012 | $0.00157 |
| Haiku 4.5 | $0.00006 | $0.00079 |
Grade A, and why
start-here 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 5d 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 — 64 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Start or resume a laboratory
Inputs
- intended laboratory outcome or first useful workflow
- existing, planned, or hybrid setup
- repository or proposed destination
- known equipment, compute, manual work, samples, data, and locations
- relevant constraints, hazards, and available evidence
Begin with partial input. Ask for only the highest-value missing information.
Procedure
- Read the nearest
AGENTS.md. Inspect the worktree, branch, recent commits, and current directory before changing files. - Determine whether the user is in this framework repository, a generated laboratory repository, or an uninitialized destination.
- When a separate lab repository is needed, collect its name, owner, and destination. Use
create-labonly after the destination is confirmed and safe. - In a lab repository, read
docs/lab/context.md,inventory.md,setup-plan.md, anddecisions.mdwhen present. Then readopensdl.yamland only the workflows needed for the task. - Classify the setup as existing, greenfield, or hybrid. Identify the first outcome before trying to inventory the entire laboratory.
- Update the shared lab files with confirmed facts, evidence, assumptions, unknowns, constraints,
and decisions. Keep the product-wide work list in
docs/development/backlog.md. - Track inventory evidence, integration, and visual-twin state separately. An inventory entry is not authority to execute equipment.
- Map the first workflow to resources, typed capabilities, simulators, manual steps, data, tests, and gaps. Prefer one complete simulation path over a broad incomplete configuration.
- Update executable manifests or workflows only from confirmed information and supported
contracts. Run
opensdl validatefor any executable file changed. - Record any custom 3D request in the lab setup plan with its purpose, source evidence, dimensions, and target workflow. An agent can build the tailored Blender scene directly in the laboratory repository. OpenSDL currently has no dedicated digital-twin command and intentionally has no model catalog.
- Hand the next task to
create-lab,orient-lab,design-lab,add-capability,add-adapter,develop-workflow,add-domain-pack, ordebug-runas appropriate. Usedesign-labwhen the open question is physical or interface design rather than OpenSDL configuration.
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.
- 5d ago First seen · 64 lines · 61 tokens per session scan A 74afb216c517
start-here is a skill published in the GitHub repository fl-sean03/OpenSDL (102 stars, last pushed 5d ago), licensed Apache-2.0. It adds 61 tokens to every session and 786 once invoked, about $0.0003 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
scientific-tool-onboarding
Use when evaluating, adding, or upgrading ScholarAIO support for a scientific computing tool, especially integration-gate review, official docs ingestion, toolref integration, lightweight skill design, and end-to-end CLI verification.
bioinformatics
Use when working on bioinformatics workflows such as alignment, variant calling, phylogenetics, or protein-structure analysis, especially across BLAST, minimap2, samtools, bcftools, MAFFT, IQ-TREE, or ESMFold.
lammps
Use when working on classical materials simulations with LAMMPS, including potential selection, shock or deformation setups, thermodynamic runs, or structure analysis for solids and nanomaterials.
paper-guided-reading
Use when the user wants guided reading, deep reading, or structured analysis of a single paper, starting from fuzzy keywords or a research question.
paper-writing
Use when the user wants help drafting or revising a research paper section, including Introduction, Related Work, Method, Results, Discussion, or Conclusion.
paper2any
Use when the user explicitly requests Paper2Any or a Paper2Any benchmark for paper-to-figure, PPT, poster, video, DrawIO, PDF-to-PPT, or related workflows through the isolated ScholarAIO sidecar.