dev

A one-command setup for a local web-development environment, including the development server, API mocks, a branch-specific HTTPS address, and a browser-testing session.

In plain words
What is it for?
Use it to start, inspect, share, or stop a branch’s local app environment before UI testing or development.
Why use it?
It avoids starting and coordinating these separate tools by hand, especially when working across branches or worktrees. It can also reuse an existing setup when resuming work.

Command

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 commands/yonatangross/orchestkit/dev
Clone the repo
git clone --depth 1 https://github.com/yonatangross/orchestkit
Per session 76 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 3,161 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.00076 $0.03161
Opus 5 $0.00038 $0.01580
Sonnet 5 $0.00015 $0.00632
Haiku 4.5 $0.00008 $0.00316

Measured 2d ago against content hash 30d264254264, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

dev 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.

plugins/ork/.cursor-plugin/commands/dev.md · 251 lines

How it starts

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

Auto-generated from skills/dev/SKILL.md

Source: https://github.com/yonatangross/orchestkit

/ork:dev — Lab-Stack Boot

One command boots the four moving parts of a Vercel-Labs-flavored dev loop:

  1. portless → named HTTPS https://<branch>.localhost (no port collisions across worktrees)
  2. emulate → stateful API emulators on the same origin via @emulators/adapter-next
  3. dev serverpnpm dev / npm run dev / yarn dev (auto-detected)
  4. agent-browser → pre-warmed session named after the branch

State lives in .claude/state/dev-stack.json. Teardown via /ork:dev stop reads the PIDs and signals SIGTERM in reverse boot order.

Paired with /ork:expect: the agent-browser session that /ork:dev warms is the same one /ork:expect (and the M125 #2 auto-trigger) attach to — no second startup latency on the first UI test.

When to invoke

Situation Command
Start work on a new branch /ork:dev
Resume after a session break /ork:dev (idempotent — skips already-live processes)
Tear down before deleting branch /ork:dev stop
Inspect state /ork:dev status
Share preview with stakeholder /ork:dev --share (tailnet) or /ork:dev --funnel (public)
Time-boxed live demo /ork:dev --live 4 (public funnel, 4-hour expiry)

Resuming a backgrounded dev session (CC 2.1.144+): Sessions started via claude --bg now appear in /resume alongside interactive ones, marked bg — use /resume as the direct recovery path after a crash or session end instead of navigating the agent view.

Background shell sessions (CC 2.1.154+): In claude agents, type ! <command> to run a shell command as a backgrounded session you can attach to and detach from — also available as claude --bg --exec '<command>'. Useful for long dev-loop processes (watchers, builds, servers) you want to monitor without holding a terminal.

Modes (M127)

Flag Wraps Reach Tailscale CLI
(none) portless <slug> <pkg-mgr> run dev https://<branch>.localhost only not required
--share portless --tailscale ... tailnet members on https://*.ts.net required
--funnel portless --funnel ... public on the internet required
--live N portless --funnel ... + N-hour expiry public, tracked in live-demos.jsonl required

Read the full file on GitHub · 251 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. 2d ago First seen · 251 lines · 76 tokens per session scan A 30d264254264

Subscribe to this mod's changes

dev is a command published in the GitHub repository yonatangross/orchestkit (224 stars, last pushed 2d ago), licensed MIT. It adds 76 tokens to every session and 3,161 once invoked, about $0.0004 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-30.