Track, aggregate, and report OpenClaw token usage and costs across sessions.
Coding
safeTok ↔ OpenClaw Bridge
Try itConnect safeTok Nostr DMs to your OpenClaw agent. Use OpenClaw with Claude OAuth — no Anthropic API key needed. Communicate via safeTok NIP-44 encrypted DMs...
What it does
Connect safeTok Nostr DMs to your OpenClaw agent. Use OpenClaw with Claude OAuth — no Anthropic API key needed. Communicate via safeTok NIP-44 encrypted DMs from your phone.
The skill document
safeTok ↔ OpenClaw Bridge
Want to use OpenClaw with Claude OAuth (no API key) and talk to your agent from your phone? This bridge enables two things:
- Use OpenClaw with Claude OAuth — no Anthropic API key needed.
- Communicate with your OpenClaw agent via Nostr — specifically safeTok NIP-44 DMs.
safeTok DMs appearing in OpenClaw Control UI
A bidirectional DM bridge connecting safeTok to OpenClaw via the Gateway WebSocket API. Incoming safeTok DMs are routed to a dedicated OpenClaw session; the assistant's reply is encrypted and published back to the Nostr relays — end-to-end encrypted, decentralized, no middleman.
Setup
See README.md for full setup instructions.
Quick start
export OPENCLAW_TOKEN="your-gateway-token"
export SAFETOK_PRIVATE_KEY="your-hex-priv-key"
npm install @noble/curves
node bridge.mjs
Files
| File | Purpose |
|---|---|
bridge.mjs | Main bridge process |
nip44.mjs | safeTok NIP-44 crypto primitives (encrypt/decrypt) |
Requirements
- Node.js ≥ 22
- Running OpenClaw gateway
- safeTok installed on your phone
Related skills
Use when configuring OpenClaw chat channels to send an immediate acknowledgement before the main reply starts. Supports Feishu and DingTalk, includes bilingu...
Route OpenClaw CLI requests to the right command family and profile, then verify the outcome.
Set up automatic notifications when OpenClaw gateway restarts. Use when user wants to be notified of gateway startup events via any messaging channel (iMessage, WhatsApp, Telegram, Discord, etc.).
Connect OpenClaw to local and LAN P2P AI agent meshes (JarvisMesh & OpenClawMesh). Requires explicit user consent for mDNS, LAN/WAN network access, remote delegation, key-file access, and exposing local tools. Remote traffic may transmit prompts, files, memory, media, and tool results to selected peers.
Wire Topical into OpenClaw — MCP server, inbound hook transform, and outbound webhook registration. Use when the user asks to connect Topical, set up Topical webhooks, or install the Topical OpenClaw integration.