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.
git 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/viash-component-authoring)<a href="https://agentmods.dev/rules/rebell-leader/spatialai_mcp/viash-component-authoring"><img src="https://agentmods.dev/badge/rules/rebell-leader/spatialai_mcp/viash-component-authoring.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.00055 | $0.00971 |
| Opus 5 | $0.00028 | $0.00485 |
| Sonnet 5 | $0.00011 | $0.00194 |
| Haiku 4.5 | $0.00006 | $0.00097 |
Grade A, and why
viash-component-authoring 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 8d 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 — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Viash component authoring
A Viash component = a config.vsh.yaml (metadata: arguments, resources, engines)
- a script (Python/R/Bash). Viash compiles it into a CLI, a Docker image, and a Nextflow module.
Steps
-
Identify the stage and its interface. OpenProblems components conform to a
comp_*API merged in via__merge__: /src/api/comp_<stage>.yaml. Find the right interface for the pipeline stage you're implementing (seecontext/ist-preprocessing-pipeline.md) and match its inputs/outputs exactly. -
Write
config.vsh.yaml. Use the modern flat config (nofunctionality:wrapper) withengines:/runners:(not the legacyplatforms:). Follow OpenProblems conventions: merge the stage API, build on the shared base image with a setup partial, include the standard metadata block, and label the nextflow runner with resource directives. This mirrors a realtask_ist_preprocessingcomponent:__merge__: /src/api/comp_<stage>.yaml name: my_method label: "My Method" summary: "One-line biological purpose." description: "Longer description with method context." links: documentation: "https://github.com/openproblems-bio/task_ist_preprocessing" repository: "https://github.com/openproblems-bio/task_ist_preprocessing" references: doi: "10.xxxx/xxxxx" # the method's paper arguments: - name: "--some_param" type: double default: 1.0 description: "Biologically meaningful parameter." # Note: --input/--output are usually inherited from the merged comp_<stage> API. resources: - type: python_script path: script.py engines: - type: docker image: openproblems/base_python:1 # shared base, not raw python:* __merge__: - /src/base/setup_spatialdata_partial.yaml # extra deps via setup partial - type: native runners: - type: executable - type: nextflow directives: label: [ midtime, lowcpu, lowmem ] # resource labels
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.
- 8d ago First seen · 100 lines · 55 tokens per session scan A a2fc355d1910
viash-component-authoring 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 55 tokens to every session and 971 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 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.
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.