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-mol-basic-metricsnpx skills add InternScience/MolClaw --skill molclaw-mol-basic-metricsgit 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-mol-basic-metrics)<a href="https://agentmods.dev/skills/internscience/molclaw/molclaw-mol-basic-metrics"><img src="https://agentmods.dev/badge/skills/internscience/molclaw/molclaw-mol-basic-metrics.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.00059 | $0.00468 |
| Opus 5 | $0.00030 | $0.00234 |
| Sonnet 5 | $0.00012 | $0.00094 |
| Haiku 4.5 | $0.00006 | $0.00047 |
Grade A, and why
molclaw-mol-basic-metrics 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
Molecular Basic Properties Calculation
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 calculate_mol_basic_info.
Compute a set of basic molecular properties for each SMILES.
Args:
smiles_list (List[str]): List of input SMILES strings, (e.g., ["N[C@@H](Cc1ccc(O)cc1)C(=O)O", "CC(C)C1=CC=CC=C1"])
Return:
status (str): success/error
msg (str): message
metrics (List[dict]): List of dict, each containing feature keys.
--smiles (str): A SMILES string of smiles_list
--molecular_formula (str): Molecular formula, e.g. "C9H11NO3"
--exact_molecular_weight (float): Exact molecular weight
--molecular_weight (float): Average molecular weight
--num_heavy_atoms (int): Number of heavy atoms
--num_atoms (int): Number of total atoms
--num_bonds (int): Number of bonds
--num_valence_electrons (int): Number of valence electrons
--formal_charge (int): Number of formal charge
How to use tool calculate_mol_basic_info:
response = await client.session.call_tool(
"calculate_mol_basic_info",
arguments={
"smiles_list": smiles_list
}
)
result = client.parse_result(response)
metrics = result["metrics"]
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 · 49 lines · 59 tokens per session scan A 85796a18c6d8
molclaw-mol-basic-metrics is a skill published in the GitHub repository InternScience/MolClaw (33 stars, last pushed 27d ago), licensed MIT. It adds 59 tokens to every session and 468 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
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…