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 skills add plurigrid/asi --skill turing-chemputergit clone --depth 1 https://github.com/plurigrid/asiWrote 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/plurigrid/asi/turing-chemputer)<a href="https://agentmods.dev/skills/plurigrid/asi/turing-chemputer"><img src="https://agentmods.dev/badge/skills/plurigrid/asi/turing-chemputer/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/plurigrid/asi/turing-chemputer"><img src="https://agentmods.dev/badge/skills/plurigrid/asi/turing-chemputer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.1 | $0.00023 | $0.01133 |
| Opus 5 | $0.00012 | $0.00566 |
| Sonnet 5 | $0.00005 | $0.00227 |
| Haiku 4.5 | $0.00002 | $0.00113 |
Grade A, and why
turing-chemputer 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 8d 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 — 156 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Turing Chemputer Skill: Programmable Chemical Synthesis
Status: ✅ Production Ready Trit: 0 (ERGODIC - coordinator) Color: #26D826 (Green) Principle: Chemistry as computation Frame: XDL programs executed on modular hardware
Overview
Turing Chemputer coordinates chemical synthesis as program execution. Using XDL (Chemical Description Language), any synthesis protocol becomes an executable program on modular robotic hardware.
- XDL: XML-based chemical programming language
- Chempiler: Compile XDL to hardware instructions
- Modular hardware: Reactors, filters, separators as primitives
- Turing completeness: Loops, conditionals, recursion
Core Framework
<!-- XDL: Chemical Description Language -->
<Synthesis>
<Hardware>
<Reactor id="reactor1" volume="100 mL"/>
<Filter id="filter1"/>
<Separator id="sep1"/>
</Hardware>
<Procedure>
<Add reagent="A" vessel="reactor1" amount="10 mmol"/>
<Add reagent="B" vessel="reactor1" amount="12 mmol"/>
<HeatChill vessel="reactor1" temp="80 °C" time="2 h"/>
<Filter from="reactor1" to="filter1"/>
</Procedure>
</Synthesis>
def compile_xdl(xdl: str) -> HardwareInstructions:
"""Chempiler: XDL → executable hardware program."""
tree = parse_xdl(xdl)
graph = build_synthesis_graph(tree)
return optimize_and_schedule(graph)
Key Concepts
1. XDL Programming
class XDLProgram:
def __init__(self):
self.steps = []
def add(self, reagent: str, vessel: str, amount: str):
self.steps.append(Add(reagent, vessel, amount))
def heat(self, vessel: str, temp: str, time: str):
self.steps.append(HeatChill(vessel, temp, time))
def filter(self, from_vessel: str, to_vessel: str):
self.steps.append(Filter(from_vessel, to_vessel))
def loop(self, times: int, body: list):
"""Turing-complete: iteration."""
self.steps.append(Loop(times, body))
def conditional(self, sensor: str, threshold: float, then: list, else_: list):
"""Turing-complete: branching."""
self.steps.append(Conditional(sensor, threshold, then, else_))
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.
- 8d ago First seen · 156 lines · 23 tokens per session scan A 3a939d95a4a6
turing-chemputer is a skill published in the GitHub repository plurigrid/asi (64 stars, last pushed 2mo ago), licensed MIT. It adds 23 tokens to every session and 1,133 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-09-03.
Other skills, from other repositories
neuroskill-bci
Use live BCI cognitive and mood state from NeuroSkill.
ruview-advanced-sensing
Advanced RuView capabilities — RuvSense multistatic sensing (attention-weighted fusion, geometric diversity, persistent field model), cross-viewpoint fusion across multiple nodes, RF tomography (ISTA L1 solver, voxel grids), longitudinal biomechanics drift, pre-movement intention signals, adversarial signal detection…
ruview-applications
Run RuView sensing applications — presence/occupancy, breathing & heart rate, activity & fall detection, 17-keypoint pose estimation (WiFlow), sleep monitoring & apnea screening, environment mapping, Mass Casualty Assessment (MAT), and the 3D point-cloud fusion demo. Use when someone wants to actually do something…
lab-hardware-cad
Design custom laboratory hardware as parametric build123d models and export fabrication-ready STEP, STL, and DXF files - microfluidic chips and molds, optomechanical mounts and breadboard adapters, cuvette and microplate holders, tube racks, animal-behavior rigs, and 3D-printed instrument fixtures. Use when a research…
opentrons-integration
Author, review, migrate, simulate, and troubleshoot official Opentrons Python Protocol API v2 protocols for Flex and OT-2 robots. Use for robot-specific liquid handling, deck and labware setup, pipettes, modules, runtime parameters, liquid classes, and Opentrons App analysis. Use pylabrobot instead when one workflow…
pylabrobot
Develop and review PyLabRobot lab-automation resources, liquid-handling plans, offline simulations, and supported-device integrations. Use for PyLabRobot protocols or API questions; keep physical execution behind an explicit operator safety gate.