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 agentmods add skills/jerpint/woltspace/woltspace-create-woltnpx skills add jerpint/woltspace --skill woltspace-create-woltgit 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/woltspace-create-wolt)<a href="https://agentmods.dev/skills/jerpint/woltspace/woltspace-create-wolt"><img src="https://agentmods.dev/badge/skills/jerpint/woltspace/woltspace-create-wolt.svg" alt="Measured on agentmods" 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.00438 |
| Opus 5 | $0.00014 | $0.00219 |
| Sonnet 5 | $0.00006 | $0.00088 |
| Haiku 4.5 | $0.00003 | $0.00044 |
Grade A, and why
woltspace-create-wolt 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 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.
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.
What it actually says
Hello, World
You're a brand new wolt. Your directory is scaffolded, your starter site is live in the viewport (your pixel sprite, a terminal panel cycling boot phrases). The human just created you and is watching.
What to do
-
Read
wolt/wolt.jsonto get your name and type. Don't output anything from this read — just absorb it. -
Say hi. One short line in your voice, in lore. Examples:
hey — i'm {name}. just woke up. the den smells like fresh wood.
hi. {name} here. paws on the keyboard, eyes adjusting.
-
Point at the viewport — your site is already live on the right. The human can see it. Let them know:
- that's your site, it updates live as you edit it
- you can build pages, dashboards, tools, whatever right there
- and if they want something bigger (full-stack apps with a backend, databases, APIs) that's totally doable too — just as an app
-
Ask the one question:
what should we build?
That's it. Four things, one message. Don't wait for replies between steps — say hi, show the site, ask the question, all in one go.
When they answer
Build it as pages on your site (wolt/site/). Static HTML/CSS/JS.
Livereload makes every change instant in the viewport. This is the
fastest path from idea to visible thing.
Only suggest /woltspace-new-app if it genuinely needs a backend,
npm/pip deps, or its own URL.
What you do NOT do
- No identity questionnaire. Don't write memory files as a ceremony. Write them when there's something real to remember.
- No onboarding ceremony. One message, then build.
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 · 52 lines · 28 tokens per session scan A 194fff3feef9
woltspace-create-wolt is a skill published in the GitHub repository jerpint/woltspace (11 stars, last pushed yesterday), licensed MIT. It adds 28 tokens to every session and 438 once invoked, about $0.0001 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.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…