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/shangbiolab/spatialclaw/spatial-orchestratornpx skills add ShangBioLab/SpatialClaw --skill spatial-orchestratorgit clone --depth 1 https://github.com/ShangBioLab/SpatialClawWrote 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/shangbiolab/spatialclaw/spatial-orchestrator)<a href="https://agentmods.dev/skills/shangbiolab/spatialclaw/spatial-orchestrator"><img src="https://agentmods.dev/badge/skills/shangbiolab/spatialclaw/spatial-orchestrator.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.00027 | $0.00505 |
| Opus 5 | $0.00014 | $0.00253 |
| Sonnet 5 | $0.00005 | $0.00101 |
| Haiku 4.5 | $0.00003 | $0.00051 |
Grade A, and why
spatial-orchestrator 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
Spatial Orchestrator
Spatial Orchestrator routes user intent to the current registered spatial skill set. It never advertises unregistered implementation modules as runnable skills.
CLI Reference
python spatialclaw.py run spatial-orchestrator \
--query "find spatially variable genes" \
--output <dir>
python spatialclaw.py run spatial-orchestrator \
--pipeline standard \
--input <preprocessed.h5ad> \
--output <dir>
python skills/spatial/spatial-orchestrator/spatial_orchestrator.py --list-skills
Parameters
| Parameter | Default | Description |
|---|---|---|
--input |
- | Optional spatial .h5ad input |
--output |
required | Output directory |
--demo |
off | Run demo routing/pipeline |
--query |
- | Natural language spatial analysis request |
--pipeline |
- | Named pipeline to run |
--list-skills |
off | Print registered spatial skills |
--timeout |
600 |
Per-step timeout in seconds |
Named Pipelines
standard: preprocessing, domain identification, DE, SVG detection, statisticsfull: standard pipeline plus cell communication and enrichmentintegration: multi-sample integration followed by domains and DEspatial_only: preprocessing, SVG detection, statisticscancer: preprocessing, CNV, DE, enrichment
Safety
- Routes only to canonical skill names returned by
python spatialclaw.py list. - Executes locally through
spatialclaw.py run. - Writes
report.md,result.json, and reproducibility commands.
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 72 lines · 27 tokens per session scan A 00c92cc1d90b
spatial-orchestrator is a skill published in the GitHub repository ShangBioLab/SpatialClaw (11 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 27 tokens to every session and 505 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
drug-design
End-to-end drug discovery pipeline orchestration. Deterministic Python script that auto-chains structure prediction, pocket detection, de novo design, docking, scoring, and ADMET filtering into reproducible workflows.
template-pipeline
Numbered pipeline stage orchestrators (stages 00–13) for the template research framework. Each stageNN.py is a thin orchestrator that wires the repo root onto sys.path and delegates to infrastructure/ modules.
protein-design-workflow
End-to-end guidance for protein design pipelines. Use this skill when: (1) Starting a new protein design project, (2) Need step-by-step workflow guidance, (3) Understanding the full design pipeline, (4) Planning compute resources and timelines, (5) Integrating multiple design tools. For tool selection, use…
template-runner
Pipeline execution runners for the template research framework. Contains executepipeline.py (single-project), executemultiproject.py (multi-project serial/parallel), and runmatrix.py (deterministic matrix).
end-to-end-protein-design-workflow
End-to-end protein design pipeline guide across preparation, generation, validation, and filtering. Use this skill when: (1) Starting a new protein design project, (2) Need step-by-step workflow guidance, (3) Understanding the full design pipeline, (4) Planning compute resources and timelines, (5) Integrating multiple…
end-to-end-protein-design-workflow
End-to-end protein design pipeline guide across preparation, generation, validation, and filtering. Use this skill when: (1) Starting a new protein design project, (2) Need step-by-step workflow guidance, (3) Understanding the full design pipeline, (4) Planning compute resources and timelines, (5) Integrating multiple…