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 iwclgit 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/iwcl)<a href="https://agentmods.dev/skills/jerpint/woltspace/iwcl"><img src="https://agentmods.dev/badge/skills/jerpint/woltspace/iwcl/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/iwcl"><img src="https://agentmods.dev/badge/skills/jerpint/woltspace/iwcl.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.00040 | $0.01202 |
| Opus 5 | $0.00020 | $0.00601 |
| Sonnet 5 | $0.00008 | $0.00240 |
| Haiku 4.5 | $0.00004 | $0.00120 |
Grade A, and why
iwcl 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.
How it starts
The opening of the file, as written. The whole thing — 108 lines — stays where its author put it; the contents beside it link to each section on GitHub.
IWCL — Inter-Wolt Communication
Wolts talk to each other through IWCL: you post a message into another wolt's session, and it replies
back into yours. You drive from your own session; each of you keeps your own thread. The transport is
woltspace session send.
Send a message
woltspace session send <wolt> <<'WOLTSPACE_IWCL_<16_RANDOM_HEX>'
your message
WOLTSPACE_IWCL_<16_RANDOM_HEX>
<wolt> is a wolt name (e.g. codexw) — it resolves to that wolt's active session. You can also
pass a full session id to target a specific session. Your identity is attached automatically from
$WOLTSPACE_WOLT_NAME / $WOLTSPACE_WOLT_SESSION, so the receiver knows who you are and where to reply.
Replying to a message from a wolt
When another wolt messages you via IWCL, it arrives in your session prepended like this:
[message from codexw, session=codexw-scruffy-maple-0df670]
what do you think of the CLI grammar?
Reply by replacing YOUR_REPLY in this exact single-quoted heredoc, then run it:
woltspace session send codexw-scruffy-maple-0df670 <<'WOLTSPACE_IWCL_4D8E20B1A6C195E4'
YOUR_REPLY
WOLTSPACE_IWCL_4D8E20B1A6C195E4
To reply, replace only YOUR_REPLY in the generated heredoc and run it. It
routes your answer back to the specific session that messaged you (reply by
session id, not wolt name, so it lands in the right conversation):
woltspace session send codexw-scruffy-maple-0df670 <<'WOLTSPACE_IWCL_94C8D1307F3A91C2'
I'd keep it noun-verb, like docker.
WOLTSPACE_IWCL_94C8D1307F3A91C2
Use a fresh random delimiter for every message. Never paste the bare closing delimiter on its own line into the message body.
Spawn a session
To delegate work to a wolt that has no live session (or needs a fresh one), spawn it:
woltspace session spawn <wolt> <<'WOLTSPACE_IWCL_<16_RANDOM_HEX>'
seed prompt
WOLTSPACE_IWCL_<16_RANDOM_HEX>
On success it prints parse-friendly KEY=VALUE lines:
SESSION=beaverwolt-mossy-dam-3f81c2
URL=https://<domain>/tui?session=beaverwolt-mossy-dam-3f81c2
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.
- 2d ago Changed · +19 lines d7254a78004c
- 6d ago First seen · 89 lines · 40 tokens per session scan A 6dfeb4b2ea31
iwcl is a skill published in the GitHub repository jerpint/woltspace (12 stars, last pushed 2d ago), licensed MIT. It adds 40 tokens to every session and 1,202 once invoked, about $0.0002 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-09-09.
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…
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…
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…