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.
npx skills add prevu-cloud/prevu --skill prevu-flowsgit clone --depth 1 https://github.com/prevu-cloud/prevuWrote 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/prevu-cloud/prevu/prevu-flows)<a href="https://agentmods.dev/skills/prevu-cloud/prevu/prevu-flows"><img src="https://agentmods.dev/badge/skills/prevu-cloud/prevu/prevu-flows/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/prevu-cloud/prevu/prevu-flows"><img src="https://agentmods.dev/badge/skills/prevu-cloud/prevu/prevu-flows.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.00100 | $0.01213 |
| Opus 5.5 | $0.00040 | $0.00485 |
| Sonnet 5.5 | $0.00020 | $0.00243 |
| Haiku 4.5 | $0.00010 | $0.00121 |
Grade A, and why
prevu-flows 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 1mo 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 — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Prevu - Workflow Flows
Two multi-step user-facing scenarios that wire the prevu CLI into a coherent loop. Each has its own playbook in references/. Load this skill when the user's intent is a workflow, not a single command. For command-level reference (every flag, every exit code), the prevu skill is the source.
Flow A - Mirror local dev to the user's phone (the AFK loop)
Read references/mirror-dev.md when the user wants to keep iterating with you while away from their laptop. Trigger phrases:
- "I'm heading out, can you keep working on this?"
- "Mirror this to Prevu / spin up a remote dev env"
- "I want to review changes on my phone tonight"
- "Set up so I can drive it from mobile"
- "Keep coding while I'm AFK"
The shape of the loop:
user (phone): "change X"
down
you: edit locally -> commit -> push
down
env: pulls -> dev server hot-reloads
down
user (phone): refreshes preview URL -> "no, do Y"
down ... repeat until accepted ...
Crucial: Prevu is the preview target, not the editing machine. Edits happen in the user's local checkout where their files, history, and secrets live. The env only sees what you push. Don't dual-edit.
Flow B - Share a WIP preview URL
Read references/share-preview.md when the user wants someone else (teammate, designer, PM, or themselves later from a different device) to see in-progress work without waiting for a deploy. Trigger phrases:
- "Show this to the backend team"
- "Send my designer a preview link"
- "I want a shareable URL for this branch"
- "Get this in front of "
The shape of the flow is shorter than mirror-dev: provision (or reuse) -> push the branch -> install + start dev server -> expose HTTPS -> hand back one URL. Once the URL is sent, you're done. No iterate loop unless the user comes back with feedback.
Decision tree - which flow?
| User said... | Use |
|---|---|
| "Going AFK / keep coding / drive from mobile" | Flow A (mirror-dev) |
| "Show / share / send" + a person or audience | Flow B (share-preview) |
| "Just create a Prevu env" with no further intent | The prevu skill - env create is enough |
| "Deploy" / "production" | Neither - Prevu is for preview environments before production |
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 1mo ago First seen · 97 lines · 0 tokens per session scan A 4eb08d22c04d
prevu-flows is a skill published in the GitHub repository prevu-cloud/prevu (11 stars, last pushed 4mo ago), licensed MIT. It adds 100 tokens to every session and 1,213 once invoked, about $0.0004 per session on Opus 5.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.
Other skills, from other repositories
csv
CSV data processing — view, filter, convert, merge tabular data. Zero barrier — use with x-cmd, Python, or awk. Use for "csv", "data", "table", "spreadsheet", "conversion".
git
Git and code hosting platform management — GitHub, GitLab, Codeberg, Forgejo. Zero barrier — install x-cmd and manage repos from the terminal. Use for "git", "github", "gitlab", "repo", "pull request", "code hosting".
work
Handle issue/PR work items with worktree isolation. Triggered by "/work [issuelink|description]" to start focused work.
atmos-vendoring
Component vendoring: vendor.yaml and component.yaml manifests, immutable vendor.lock.yaml receipts, pulling from Git/S3/HTTP/OCI/Terraform Registry, --stack/--labels/--tags selector composition, native vendor update, clean, diff, config, and reviewed local component copies.
atmos-hooks
Atmos hooks: lifecycle events, hook kinds, command/store/git/security hooks, step/steps hooks, when: conditions, scoping and overrides, toolchain integration, --skip-hooks, and Atmos Pro/local output.
atmos-git
Atmos Git and GitOps: git.repositories, clone/pull/status/diff/commit/push/clean, local Git hook shims and hook env vars, signed commits, managed workdirs, fork-PR trust gate (clone gate and posting gate), and auth via identities or github/sts.