Borrowing it
Nothing to install: this file belongs to Rebell-Leader/SpatialAI_MCP. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Rebell-Leader/SpatialAI_MCP/main/.agents/skills/openproblems-submission/SKILL.mdgit 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/skills/rebell-leader/spatialai_mcp/openproblems-submission)<a href="https://agentmods.dev/skills/rebell-leader/spatialai_mcp/openproblems-submission"><img src="https://agentmods.dev/badge/skills/rebell-leader/spatialai_mcp/openproblems-submission/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/rebell-leader/spatialai_mcp/openproblems-submission"><img src="https://agentmods.dev/badge/skills/rebell-leader/spatialai_mcp/openproblems-submission.svg" alt="Reviewed on agentmods" width="80" 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.00055 | $0.00636 |
| Opus 5 | $0.00028 | $0.00318 |
| Sonnet 5 | $0.00011 | $0.00127 |
| Haiku 4.5 | $0.00006 | $0.00064 |
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 10d 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 — 52 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.
Don't
- Don't claim the server can build/benchmark/validate-submission automatically —
build_openproblems_method,run_openproblems_benchmark, andvalidate_openproblems_submissionare roadmap. Use the validation/analysis tools that exist, and run the build/benchmark steps via local CLIs.
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.
- 10d ago First seen · 52 lines · 55 tokens per session scan A 4fdd9a4d93bd
openproblems-submission is a skill published in the GitHub repository Rebell-Leader/SpatialAI_MCP (4 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 55 tokens to every session and 636 once invoked, about $0.0003 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 skills, from other repositories
instrument-data-to-allotrope
Convert laboratory instrument output files (PDF, CSV, Excel, TXT) to Allotrope Simple Model (ASM) JSON format or flattened 2D CSV. Use this skill when scientists need to standardize instrument data for LIMS systems, data lakes, or downstream analysis. Supports auto-detection of instrument types. Outputs include full…
exploratory-data-analysis
Perform bounded, local exploratory analysis of explicitly supported scientific files. Use for redacted CSV/TSV/JSON profiles; optional NumPy, HDF5, FASTA/FASTQ, and basic image metadata inspection; missingness/leakage audits; outlier and transformation sensitivity; and rigorous EDA report scaffolds. Other domain…
matlab
Build, review, migrate, and safely plan MATLAB or GNU Octave numerical workflows, including arrays, tabular/time data, tests, projects, graphics, MAT files, and explicit Python interoperability.
phylogenetics
Build and analyze phylogenetic trees using MAFFT (multiple alignment), IQ-TREE 2 (maximum likelihood), and FastTree (fast NJ/ML). Visualize with ETE3 or FigTree. For evolutionary analysis, microbial genomics, viral phylodynamics, protein family analysis, and molecular clock studies.
research-engineer
An uncompromising Academic Research Engineer. Operates with absolute scientific rigor, objective criticism, and zero flair. Focuses on theoretical correctness, formal verification, and optimal implementation across any required technology.
mapping-to-snomed
Maps clinical concept spans extracted by OpenMed to SNOMED CT concepts through a USER-SUPPLIED terminology server (the user's own Ontoserver, Snowstorm, or UMLS/UTS), never a bundled vocabulary. Use when the user wants to code findings, disorders, procedures, body structures, or substances to SNOMED CT, run an ECL…