Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Encode and decode Cashu tokens that are hidden inside emojis using Unicode variation selectors.
Encode and decode Cashu tokens that are hidden inside emojis using Unicode variation selectors.
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Then review README.md for any prerequisites, environment setup, or post-install checks. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Then review README.md for any prerequisites, environment setup, or post-install checks. Summarize what changed and any follow-up checks I should run.
This skill helps agents decode Cashu tokens received as emoji (and encode tokens for sending), and it also supports general hidden messages inside emojis. If the decoded text starts with cashu, itβs likely a Cashu token. Otherwise treat it as a plain hidden message.
Some services embed a cashu... token into an emoji using Unicode variation selectors (VS1..VS256). Chat apps often display only the emoji, but preserve the hidden selector characters. Important: many messengers can truncate or normalize Unicode. If the variation selectors are lost, the embedded token cannot be recovered.
git clone https://github.com/robwoodgate/cashu-emoji.git cd cashu-emoji npm ci # decode a whole message (recommended) node ./bin/cashu-emoji.js decode "<paste message>" # decode and print mint/unit/amount if itβs a cashu token node ./bin/cashu-emoji.js decode "<paste message>" --metadata # decode as structured JSON (agent-friendly) node ./bin/cashu-emoji.js decode "<paste message>" --metadata --json # encode a hidden message node ./bin/cashu-emoji.js encode "π₯" "hello from inside an emoji" # encode a cashu token node ./bin/cashu-emoji.js encode "π₯" "cashuB..."
Input: entire message text (may include other text/emojis) Output: the embedded UTFβ8 text, usually a cashuA.../cashuB... token node ./bin/cashu-emoji.js decode "<paste entire message>" Decode semantics (important): the decoder ignores normal characters until it finds the first variation-selector byte, then collects bytes until the first normal character after that payload begins.
Input: a carrier emoji (recommend π₯) and a token string Output: an emoji string that visually looks like the emoji but contains the hidden token node ./bin/cashu-emoji.js encode "π₯" "cashuB..." Tip: some messengers are less likely to deliver a truncated/corrupted emoji-token if any normal text follows it (even a single character). Itβs not required, just a delivery reliability trick. Tip (Telegram): sending the emoji-token inside a code block / βmonospaceβ formatting can help preserve the hidden characters and makes it easier to tap-to-copy.
To sanity-check the decoded token without redeeming it, you can request metadata. For programmatic/agent use, prefer JSON output: node ./bin/cashu-emoji.js decode "<message>" --metadata --json Example JSON response (Cashu token): { "text": "cashuB...", "isCashu": true, "metadata": { "mint": "https://mint.example", "unit": "sat", "amount": 21 }, "metadataError": null } Example JSON response (plain hidden message): { "text": "hello from inside an emoji", "isCashu": false } node ./bin/cashu-emoji.js decode "<message>" --metadata This prints mint/unit/amount using @cashu/cashu-ts getTokenMetadata() (no mint calls).
A decoded cashu... token is a bearer asset. Treat it like cash. --metadata is a local parse. It canβt prove the token is unspent/valid. If decode returns a partial token or nonsense, the messenger likely munged the variation selectors; ask for the token to be re-sent (often with some trailing normal text after the emoji token).
src/emoji-encoder.ts: core encode/decode bin/cashu-emoji.js: CLI wrapper examples/: test vectors
This tool only encodes/decodes text. It does not spend funds.
Agent frameworks, memory systems, reasoning layers, and model-native orchestration.
Largest current source with strong distribution and engagement signals.