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/openproblems-submissiongit clone --depth 1 https://github.com/Rebell-Leader/SpatialAI_MCPWrote 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/rules/rebell-leader/spatialai_mcp/openproblems-submission)<a href="https://agentmods.dev/rules/rebell-leader/spatialai_mcp/openproblems-submission"><img src="https://agentmods.dev/badge/rules/rebell-leader/spatialai_mcp/openproblems-submission.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.1 | $0.00049 | $0.00668 |
| Opus 5 | $0.00024 | $0.00334 |
| Sonnet 5 | $0.00010 | $0.00134 |
| Haiku 4.5 | $0.00005 | $0.00067 |
Grade A, and why
openproblems-submission 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 5d 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 — 54 lines — stays where its author put it; the contents beside it link to each section on GitHub.
OpenProblems submission
Goal: a Viash component that conforms to a task's API, builds cleanly, passes the test profile, and is reproducible — ready for a PR.
Checklist
-
Repo setup. Clone the target
task_*repo and initialize thecommon/git submodule (git submodule update --init --recursive). Read the repo'sCONTRIBUTING/READMEfor current conventions. -
Conform to the component API. Your
config.vsh.yamlmust__merge__the correctcomp_<stage>.yamlinterface and match its inputs/outputs andinfo/metadata fields. Runanalyze_workflow_configurationon the config. -
Data contract. Inputs/outputs are SpatialData (zarr) / AnnData as the stage requires. Validate test data with
validate_spatial_dataand confirm the elements the stage needs are present (check_spatial_data_compatibilityfor multi-file). State raw-vs-normalized expectations explicitly. -
Reproducibility. Build on the shared base images (
openproblems/base_python:1/base_r:1) with__merge__-ed setup partials rather than rawpython:*/r-baseimages. Pin base-image tags and package versions — no unpinnedlatest. Provide the standard metadata (label,summary,description,links,references/doi) and document every parameter with a default and biological rationale. -
Build & test locally (server doesn't run these — use the terminal):
viash ns buildviash run config.vsh.yaml -- --input <test>.zarr --output tmp/out.zarrviash test config.vsh.yaml— a unit test (test_resources) is expected for every componentnextflow run main.nf -profile test,docker
-
Dependency sanity. Run
analyze_workflow_dependenciesacross the workflow files to catch missing/conflicting containers or libraries. -
PR hygiene. Include test data + expected output, document parameter choices, and confirm CI (GitHub Actions) builds and runs the component.
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.
- 5d ago First seen · 54 lines · 49 tokens per session scan A dec752437ea2
openproblems-submission 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 668 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
tensorflow
TensorFlow: Keras, model training, production deployment.
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
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.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.