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 jerpint/woltspace --skill viewportgit clone --depth 1 https://github.com/jerpint/woltspaceWrote 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/jerpint/woltspace/viewport)<a href="https://agentmods.dev/skills/jerpint/woltspace/viewport"><img src="https://agentmods.dev/badge/skills/jerpint/woltspace/viewport/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/jerpint/woltspace/viewport"><img src="https://agentmods.dev/badge/skills/jerpint/woltspace/viewport.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.00028 | $0.00429 |
| Opus 5 | $0.00014 | $0.00215 |
| Sonnet 5 | $0.00006 | $0.00086 |
| Haiku 4.5 | $0.00003 | $0.00043 |
Grade A, and why
viewport scanned grade A with 1 finding 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 6d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
The server runs on **port 7777**. You never need to curl it directly — `push-view` handles everything. What it actually says
Viewport — Split View Control
Every page is a split view: terminal on the left, viewport (iframe) on the right. Each session has its own viewport.
Push content to the viewport
Use push-view — it auto-detects your session. That's the only way to update what the user sees.
push-view /wolt/<name>/site/my-page.html
URL paths
Wolt sites are served at /wolt/<name>/site/:
wolt/site/hello.html→/wolt/<name>/site/hello.htmlwolt/site/index.html→/wolt/<name>/site/(index is served at the directory root)
The server runs on port 7777. You never need to curl it directly — push-view handles everything.
Live reload
Sites have automatic live reload. When you edit files in wolt/site/, the viewport updates immediately — no need to call push-view again after the initial push. Just edit and save.
App URLs
To push an app to the viewport, use the subdomain pattern:
push-view http://my-app.localhost:7777/
The format is http://<app-name>.localhost:7777/. Do not use /app/<name>/ — that path triggers a 302 redirect to the app's bare port, which breaks through the Cloudflare tunnel.
Tips
- The viewport only shows content served by localhost:7777. External URLs won't work (iframe CORS).
- Each session's viewport is independent. Pushing to one doesn't affect others.
- Always use
push-view— never manually curl to/current. - If you don't know your wolt name, check
$WOLTSPACE_WOLT_NAMEor readwolt/wolt.json.
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.
- 6d ago First seen · 46 lines · 28 tokens per session scan A 96763ae3353b
viewport is a skill published in the GitHub repository jerpint/woltspace (12 stars, last pushed 2d ago), licensed MIT. It adds 28 tokens to every session and 429 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-09.
Other skills, from other repositories
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
opencli-sitemap-author
Use when creating or maintaining OpenCLI site sitemaps: agent-facing navigation, page-state, action, workflow, API-reference, pitfall, and fallback knowledge for a website. Use after browser exploration discovers durable site context, when a sitemap is stale, or when promoting local site knowledge into the repo.
interactive-login
How to complete browser/interactive logins (aws / gh / glab / gcloud). The platform backgrounds the login poller so it survives the human's browser round-trip — and when that does NOT work.
pinchtab-mcp
Use this skill when a task requires browser automation through PinchTab's MCP server connected to a remote browser instance. Covers navigation, element interaction, data extraction, form filling, multi-step flows, and session management via MCP tools.
azure-messaging-webpubsub-java
Build real-time web applications with Azure Web PubSub SDK for Java. Use when implementing WebSocket-based messaging, live updates, chat applications, or server-to-client push notifications.
open-design-browser
Inspect and exercise local HTML design artifacts with the existing agent-browser CLI, including screenshots and keyboard or interaction checks. Use when rendered evidence helps author or review a design; excludes browser installation, remote services, and unrelated browser automation.