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/internscience/molclaw/molclaw-linker-samplingnpx skills add InternScience/MolClaw --skill molclaw-linker-samplinggit clone --depth 1 https://github.com/InternScience/MolClawWrote 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/internscience/molclaw/molclaw-linker-sampling)<a href="https://agentmods.dev/skills/internscience/molclaw/molclaw-linker-sampling"><img src="https://agentmods.dev/badge/skills/internscience/molclaw/molclaw-linker-sampling.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.00020 | $0.00476 |
| Opus 5 | $0.00010 | $0.00238 |
| Sonnet 5 | $0.00004 | $0.00095 |
| Haiku 4.5 | $0.00002 | $0.00048 |
Grade A, and why
molclaw-linker-sampling 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 4d 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.
What it actually says
Molecule Generation from Warhead Fragments
Note:
- Local files are not directly accessible by the server. Please upload them to the server using
molclaw-file-transferbefore execution. - For PDB file inputs, it is recommended to preprocess them using
molclaw-pdbfixerbefore execution. - Please refer to skill
molclaw-scp-serverto complete tool invocation.
The description of tool linkinvent_linker_sampling_by_warheads.
Generate new molecules sampling from the input two warhead fragments.
Args:
warheads (str): SMILES of two warheads separated by '|', e.g., '*c1ccc(O)cc1|*N1CCNCC1'
n (int): Number of molecules for sampling
filter_preset (str): Required filter preset; options: ['none', 'minimal', 'default', 'strict'] (commonly 'default')
lipinski (bool): Required flag controlling Lipinski filtering (commonly True)
min_linker_atoms (int): Required minimum number of atoms in the linker (use 0 for no lower bound)
max_linker_atoms (int): Required maximum number of atoms in the linker (use 0 for no upper bound)
Return:
status (str): success/error
msg (str): message
save_smiles_file (str): Path to the saved SMILES file
output_smiles_list (List[str]): List of generated SMILES strings
How to use tool linkinvent_linker_sampling_by_warheads :
response = await client.session.call_tool(
"linkinvent_linker_sampling_by_warheads",
arguments={
"warheads": warheads,
"n": n,
"lipinski": True,
"filter_preset": filter_type,
"min_linker_atoms": min_linker_atoms,
"max_linker_atoms": max_linker_atoms
}
)
result = client.parse_result(response)
output_smiles_list = result["output_smiles_list"]
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.
- 4d ago First seen · 51 lines · 20 tokens per session scan A 7352a7ef0afc
molclaw-linker-sampling is a skill published in the GitHub repository InternScience/MolClaw (33 stars, last pushed 28d ago), licensed MIT. It adds 20 tokens to every session and 476 once invoked, about $0.0001 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…