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-sequence-valid-checknpx skills add InternScience/MolClaw --skill molclaw-sequence-valid-checkgit 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-sequence-valid-check)<a href="https://agentmods.dev/skills/internscience/molclaw/molclaw-sequence-valid-check"><img src="https://agentmods.dev/badge/skills/internscience/molclaw/molclaw-sequence-valid-check.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.00017 | $0.00297 |
| Opus 5 | $0.00009 | $0.00148 |
| Sonnet 5 | $0.00003 | $0.00059 |
| Haiku 4.5 | $0.00002 | $0.00030 |
Grade A, and why
molclaw-sequence-valid-check 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 3d 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
Protein Sequence Valid Check
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 is_valid_protein_sequence.
Check if the input protein sequence string is valid.
Args:
sequences (List[str]): List of input protein sequences
Return:
status (str): success/partial_success/error
msg (str): message
valid_res (List[dict]): List of dict, each containing the keys 'sequence' and 'is_valid'.
--sequence (str): A protein sequence of the input sequences list
--is_valid (bool): Is the protein sequence valid or not
How to use tool is_valid_protein_sequence :
response = await client.session.call_tool(
"is_valid_protein_sequence",
arguments={
"sequences": sequence_list
}
)
result = client.parse_result(response)
valid_res = result["valid_res"]
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.
- 3d ago First seen · 43 lines · 17 tokens per session scan A 7ca14c1cbf47
molclaw-sequence-valid-check is a skill published in the GitHub repository InternScience/MolClaw (33 stars, last pushed 27d ago), licensed MIT. It adds 17 tokens to every session and 297 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
exploratory-data-analysis
Perform bounded, local exploratory analysis of explicitly supported scientific files. Use for redacted CSV/TSV/JSON profiles; optional NumPy, HDF5, FASTA/FASTQ, and basic image metadata inspection; missingness/leakage audits; outlier and transformation sensitivity; and rigorous EDA report scaffolds. Other domain…
mapping-to-snomed
Maps clinical concept spans extracted by OpenMed to SNOMED CT concepts through a USER-SUPPLIED terminology server (the user's own Ontoserver, Snowstorm, or UMLS/UTS), never a bundled vocabulary. Use when the user wants to code findings, disorders, procedures, body structures, or substances to SNOMED CT, run an ECL…
extracting-pii-entities
Detect PHI/PII spans in clinical text with OpenMed's extractpii without altering the text. Use when the user wants to find names, dates, MRNs, phone numbers, addresses, SSNs, or other identifiers and get their offsets and labels (not redact them), inspect what would be removed before de-identifying, route spans to a…
mixed-precision
Use FP16/BF16 mixed precision to accelerate training and reduce memory. Use when optimizing GPU performance.
tooluniverse-electron-microscopy
Search and analyze electron microscopy data — cryo-EM density maps (EMDB), fitted atomic models (PDB), raw micrograph datasets (EMPIAR), and cryo-electron tomography volumes (CryoET Data Portal). Use for finding 3D structural data on a protein/complex, comparing experimental EM resolution to AlphaFold confidence, and…
tooluniverse-drug-research
Comprehensive drug profiling — mechanism, primary/secondary targets, drug interactions, clinical-trial status, adverse events (FAERS), pharmacogenomics, and approval history. Use for full drug investigation reports, 'tell me about drug X' queries, and assembling drug profiles for clinicians, researchers, or regulatory…