iwcl

iwcl is a skill for Claude Code from jerpint/woltspace. It costs 40 tokens per session (1,202 once invoked), scanned A, original, MIT.

A messaging system for sending requests to another wolt, an independent coding-agent workspace, and receiving replies in the correct session.

In plain words
What is it for?
Use it to delegate work, ask another wolt for help, collaborate on a problem, or answer a message from another wolt.
Why use it?
It supports collaboration without mixing separate agents' conversations or losing the session that should receive a reply.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: mentions Codex.

Part of the woltspace plugin — 23 skills shipped together

Good fit Use it to delegate work, ask another wolt for help, collaborate on a problem, or answer a message from another wolt.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/jerpint/woltspace/iwcl
Install

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.

Any agent
npx skills add jerpint/woltspace --skill iwcl
Clone the repo
git clone --depth 1 https://github.com/jerpint/woltspace

Made for: Claude Code.

Or install woltspace, the plugin that ships this one along with the rest of its 23 skills.

Wrote 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.

agentmods badge for iwcl

README.md
[![agentmods](https://agentmods.dev/badge/skills/jerpint/woltspace/iwcl/github.svg)](https://agentmods.dev/skills/jerpint/woltspace/iwcl)
Your own site
<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.

agentmods 80×15 button for iwcl

Your own site · 80×15
<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>
Per session 40 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,202 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00040 $0.01202
Opus 5.5 $0.00016 $0.00481
Sonnet 5.5 $0.00008 $0.00240
Haiku 4.5 $0.00004 $0.00120

Measured 1mo ago against content hash d7254a78004c, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 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.

container/skills/iwcl/SKILL.md · 108 lines

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

Read the full file on GitHub · 108 lines

Changes

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.

  1. 1mo ago Changed · +19 lines d7254a78004c
  2. 2mo ago First seen · 89 lines · 40 tokens per session scan A 6dfeb4b2ea31

Subscribe to this mod's changes

iwcl is a skill published in the GitHub repository jerpint/woltspace (22 stars, last pushed today), licensed MIT. It adds 40 tokens to every session and 1,202 once invoked, about $0.0002 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-09-09.

Related

iwcl compared with skills from other repositories

iwcl next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
iwcljerpint/woltspaceSkill22todayMITA40Claude Code
imagegenopenai/codexSkill134ktodayApache-2.0A113Codex
local-ai-agentsmicrosoft/ai-agents-for-beginnersSkill79k3d agoMITA200Claude Code, Codex
playwright-climicrosoft/playwrightSkill100ktodayApache-2.0A19Claude Code
browser-automationopenclaw/openclawSkill394ktodayMITA36Claude Code
systematic-debuggingobra/superpowersSkill315k6d agoMITA21Claude Code
next-cache-components-adoptionvercel/next.jsSkill143ktodayMITA95Claude Code