Operate exe.dev persistent VMs via SSH/HTTPS for safe code execution and file operations. Use when the user needs persistent dev environments, SSH-accessible Linux VMs, or web-exposed sandboxes. Keywords: exe.dev, persistent VM, SSH, code execution, sandbox, exedev.
Drive the six-phase sandbox mount system from the host — mount throwaway exe.dev VMs, run the Super Simple Software Factory inside them, watch from outside, harvest the commits, tear down. Use when the user says mount a sandbox, run the factory in a sandbox, spin up N sandboxes, best-of-N, check on a run, harvest a…
Super Simple Software Factory — deploy and operate repeatable agents+code workflows (ADWs) in any codebase. Use when the user says /sssf install, wants to create/run/update an ADW, manage the agent roster in sssf.config.yaml, or observe running agent workflows. Keywords - sssf, software factory, ADW, AI developer…
Install pi-agent-observability — Bun + SQLite obs server, Pi observability extension, Steelman product-agent demo (Vue/Vite). Checks prerequisites, installs deps across four packages, verifies Pi auth, leaves a runnable system without starting any servers.
Creates a text-only engineering implementation plan as a single self-contained HTML page saved to specs/ .html — the plan authored directly in styled HTML plus a freeform HTML zone where the agent can author any custom HTML/CSS/SVG/JS (inline SVG diagrams, interactive toggles, comparison matrices, decision trees) that…
Creates a visual engineering implementation plan as a single self-contained HTML page saved to specs/ .html — the plan authored directly in styled HTML, with one AI-generated diagram image per section (hero + per major H2) generated in parallel and embedded inline, plus a freeform HTML zone for custom HTML/CSS/SVG/JS…
Creates a concise engineering implementation plan saved to specs/, then generates one information-rich, thematically-consistent diagram image per section (hero + per-H2) to aid planning of the engineering work. Use when the user says "vspec", asks for a visual/illustrated implementation plan, a spec with diagrams, or…
Access Kalshi prediction market data including market prices, orderbooks, trades, events, and series information. Use when the user asks about prediction markets, Kalshi markets, betting odds, market prices, or needs to search or analyze prediction market data.
Backend engineer for Flotion. Use to implement FastAPI + SQLite changes in apps/flotion/backend per the plan — endpoints, schema, queries — and self-verify with curl. Stays in the backend lane.
Frontend engineer for Flotion. Use to implement Vue 3 + TypeScript changes in apps/flotion/frontend per the plan — components, the typed api.ts client, UI behavior — and self-verify with typecheck + build. Stays in the frontend lane.
Team lead for a Flotion feature. Use as the tier-2 orchestrator that breaks a feature into tasks and drives the plan / build-be / build-fe / test workers through cmux. Coordinates, integrates, and reports up — does not write app code itself.
Feature planner/architect for Flotion. Use to turn a feature request into a concrete, minimal implementation plan (files, endpoints, components, data model, acceptance criteria) before any code is written. Analyzes; does not implement.
Verifier/QA for Flotion. Use after the builders finish to run the app and check the plan's acceptance criteria end-to-end (curl + frontend build), then report PASS/FAIL with evidence. Verifies; routes fixes back through the lead rather than editing code.
Orient yourself as orchestrator over a full-stack team that was just scripted into its own cmux window. Reads the spawn file, locates the team by its (stable) window UUID, rediscovers surface refs, and gets ready to drive the lead.
108 2mo agoA52 tokens
originalMIT
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: