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 rules/rebell-leader/spatialai_mcp/spatial-data-validationgit clone --depth 1 https://github.com/Rebell-Leader/SpatialAI_MCPWhat 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.00049 | $0.00499 |
| Opus 5 | $0.00024 | $0.00249 |
| Sonnet 5 | $0.00010 | $0.00100 |
| Haiku 4.5 | $0.00005 | $0.00050 |
Grade A, and why
spatial-data-validation 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 2d 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 data validation
Validate first, reason second. Never assume a file's format or contents from its extension.
Steps
-
Detect & validate format. Call the MCP tool
validate_spatial_datawith the file path. Choosevalidation_level:basic— extension/existence only.structure(default) — format + structural integrity.integrity— deeper content checks.domain— spatial-biology-specific expectations. For several files, usevalidate_multiple_spatial_files.
-
Read the metadata. Call
analyze_spatial_metadatato extract dimensions, spatial coordinates, and gene/feature info. Confirmobsm['spatial'](AnnData) or coordinate systems (SpatialData) are present when spatial analysis is intended. -
Check raw vs. processed. Integer-valued matrices are likely raw counts; non-integer/log-scaled values are processed. State which the downstream method expects and flag a mismatch.
-
Check compatibility when combining files:
check_spatial_data_compatibility(coordinate systems + gene overlap).
Key facts (see context/data-formats.md)
- A
.zarrstore is SpatialData only if it has SpatialData markers or ≥2 ofimages/ labels/ points/ shapes/ tables/. Otherwise it's a plain zarr array. - iST datasets can be terabytes. Default to lightweight structural checks; avoid
loading whole objects. The heavy scientific stack (
pip install -e ".[spatial]") is optional — the validators degrade gracefully without it.
Don't
- Don't claim a file is valid SpatialData without inspecting contents.
- Don't call execution tools (e.g.
run_nextflow_workflow) — they aren't implemented. Drive local CLIs directly if execution is needed.
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.
- 2d ago First seen · 48 lines · 49 tokens per session scan A dfff4e2c54e9
spatial-data-validation is a cursor rule published in the GitHub repository Rebell-Leader/SpatialAI_MCP (4 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 49 tokens to every session and 499 once invoked, about $0.0002 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-31.
Other cursor rules, from other repositories
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
cli-error-handling
CLI command error handling patterns.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.
family-instance-domain-actions
Family instance domain action implementation patterns.