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-targetsnpx skills add ShangBioLab/SpatialClaw --skill spatial-targetsgit 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-targets)<a href="https://agentmods.dev/skills/shangbiolab/spatialclaw/spatial-targets"><img src="https://agentmods.dev/badge/skills/shangbiolab/spatialclaw/spatial-targets.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.00028 | $0.00348 |
| Opus 5 | $0.00014 | $0.00174 |
| Sonnet 5 | $0.00006 | $0.00070 |
| Haiku 4.5 | $0.00003 | $0.00035 |
Grade A, and why
spatial-targets 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 Targets
Spatial Targets summarizes spatial analysis results into exploratory biomarkers, candidate research targets, and drug annotation summaries.
Interface
Python API only. This skill is intentionally not registered for spatialclaw run or other CLI execution routing.
Research-Use Boundary
Outputs are exploratory and research-use only. They do not recommend therapies, determine clinical actionability, diagnose disease, or provide clinical decision support. In-code drug annotations are static research references, not treatment guidance.
Python API
from skills.spatial._lib.targets import run_targets
result = run_targets(adata, method="biomarker_discovery", domain_key="spatial_domain")
Capabilities
- Spatial biomarker discovery from domains or niches.
- Research target prioritization from expression and spatial specificity.
- Drug annotation against curated in-code target-drug mappings.
- Research-use evidence summary generation.
Validation
Covered by tests/spatial/test_library_only_skills.py::test_spatial_targets_smoke.
What ships with it
1 file 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 · 53 lines · 28 tokens per session scan A cb730bd62d1b
spatial-targets is a skill published in the GitHub repository ShangBioLab/SpatialClaw (11 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 28 tokens to every session and 348 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
Gene Panel Selection Workflow
End-to-end workflow for gene panel design in scRNA-seq and spatial transcriptomics, that should be STRICTLY followed: dataset understanding + smart downsampling + train/test splits, algorithmic selection (HVG/DE/RF/scGeneFit/SpaPROS), optimal sub-panel discovery (ARI vs size), biological completion with a stability…
Developmental Gene Panel Design Workflow
Panel design for DEVELOPING / dynamic systems (embryonic organs, differentiation, regeneration). The target experiment is usually a LATE / terminal stage, but the biology is a trajectory: terminal cell types are end-products of earlier lineage programs. A panel built from the target stage alone resolves terminal…
Spatial Omics Skills Index
Skills for spatial transcriptomics analysis including single-cell to spatial mapping (MOSCOT), 3D visualization (PyVista), and related spatial workflows.
consensus-interpret
Load when biologically interpreting a finished verified consensus run (consensus-domains / sc-consensus-clustering) — inline DE, marker-DB lookup, and LLM cell-type naming with mandatory marker citations + evidence-bound next-step recommendations. Skip when the consensus run failed (fix it first); forward query→skill…
spatial-annotate
Load when assigning per-spot cell-type labels on a spatial AnnData via marker-gene scoring or scRNA-reference mapping (Tangram / scANVI / CellAssign). Skip when computing spot-level cell-type proportions for multi-cell-per-spot platforms (use spatial-deconv); tissue-domain detection (use spatial-domains).
spatial-communication
Load when computing ligand-receptor cell-cell communication on a preprocessed spatial AnnData with obs[celltypekey] (default leiden) via LIANA (default), CellPhoneDB, FastCCC, or CellChat (R). Skip when running scRNA-only L-R inference (use sc-cell-communication); no cell-type labels exist (use spatial-annotate).