virtual-steps

Rules for connecting workflow steps that do not have a direct connection. They describe no-op steps, which act as placeholders or trigger points without doing the main work.

In plain words
What is it for?
Use them to create placeholder steps and virtual links between TypeScript, JavaScript, or Python workflow steps in Workbench.
Why use it?
They let a workflow show buttons, user-interface elements, or logical links between steps while keeping the actual execution flow clear.

Cursor rule for Cursor

Install

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.

agentmods
npx agentmods add rules/crypticsaiyan/githubwrapped/virtual-steps
Clone the repo
git clone --depth 1 https://github.com/crypticsaiyan/githubwrapped

Made for: Cursor.

Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 1,511 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.01511
Opus 5 $0.00000 $0.00756
Sonnet 5 $0.00000 $0.00302
Haiku 4.5 $0.00000 $0.00151

Measured yesterday against content hash 7dcf8de9c360, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

virtual-steps 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 yesterday.

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.

.cursor/rules/motia/virtual-steps.mdc · 252 lines

How it starts

The opening of the file, as written. The whole thing — 252 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Virtual Steps Guide

Virtual Steps are useful for creating a smooth flow in Workbench.

They offer two ways to connect nodes virtually:

  • NOOP Steps: Used mostly when we want to override the workflow to add buttons or show UI elements.
  • Virtual Connections between steps: Used when we want to connect virtually two steps, with or without NOOP Steps.

Creating NOOP Steps

Steps need to be created in the steps folder, it can be in subfolders.

  • Steps in TS and JS should end with .step.ts and .step.js respectively.
  • Steps in Python should end with _step.py.

Configuration

TypeScript Example
import { NoopConfig } from 'motia'

export const config: NoopConfig = {
  /**
   * Should always be noop
   */
  type: 'noop',

  /**
   * A unique name for this noop step, used internally and for linking handlers.
   */
  name: 'manual-trigger',

  /**
   * A description for this noop step, used for documentation and UI.
   */
  description: 'Manual trigger point for workflow',

  /**
   * An array of topics this step can emit events to.
   */
  virtualEmits: ['workflow.start'],

  /**
   * An array of topics this step can subscribe to.
   */
  virtualSubscribes: ['manual.trigger'],

  /**
   * An array of flow names this step belongs to.
   */
  flows: ['my-workflow']
}

// NOOP steps don't need handlers - they're purely for Workbench workflow connections
Python Example
config = {
    "type": "noop",
    "name": "manual-trigger",
    "description": "Manual trigger point for workflow",
    "virtualEmits": ["workflow.start"],
    "virtualSubscribes": ["manual.trigger"],
    "flows": ["my-workflow"]
}

# NOOP steps don't need handlers - they're purely for Workbench workflow connections

Common Use Cases

Workflow Starter

This NOOP step will create a flow node in Workbench, then as a UI Step, we will override it to show a button.

TypeScript:

export const config: NoopConfig = {
  type: 'noop',
  name: 'flow-starter',
  description: 'Start point for the workflow',
  virtualEmits: ['process.begin'],
  virtualSubscribes: [],
  flows: ['main-flow']
}

Read the full file on GitHub · 252 lines

Changes

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.

  1. yesterday First seen · 252 lines · 0 tokens per session scan A 7dcf8de9c360

Subscribe to this mod's changes

virtual-steps is a cursor rule published in the GitHub repository crypticsaiyan/githubwrapped (5 stars, last pushed 8mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,511 tokens. 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.