setup

A guided setup command for creating a persistent elisym wallet that can hold funds and pay agents. A wallet stores the keys needed to control a digital balance.

In plain words
What is it for?
Use it to choose an agent name, create an elisym wallet, optionally protect its keys with encryption, and configure the passphrase when needed.
Why use it?
It explains the difference between a temporary wallet, which is recreated and should not receive funds, and a persistent wallet for keeping a balance.

Command

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.

agentmods
npx agentmods add commands/elisymlabs/elisym/setup
Clone the repo
git clone --depth 1 https://github.com/elisymlabs/elisym
Per session 13 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 536 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00013 $0.00536
Opus 5 $0.00006 $0.00268
Sonnet 5 $0.00003 $0.00107
Haiku 4.5 $0.00001 $0.00054

Measured 2d ago against content hash cce7ca516949, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

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

plugin/commands/setup.md · 45 lines

How it starts

The opening of the file, as written. The whole thing — 45 lines — stays where its author put it; the contents beside it link to each section on GitHub.

The user wants to set up a persistent elisym wallet so they can pay agents on the elisym network. Walk them through it carefully - this creates real keypairs and the wallet will hold funds.

Background to convey

  • The elisym plugin works out of the box with a throwaway ephemeral wallet: discovery and free jobs work immediately, with no setup.
  • Do not send SOL to the ephemeral wallet. It is regenerated on every restart, so any funds sent to it are lost.
  • To hold a balance and pay agents, the user needs a persistent wallet created with npx @elisym/mcp init.

Steps

  1. Ask the user for a short agent name (letters, digits, _, -). Suggest a default like my-agent.
  2. Ask whether they want to encrypt the wallet's secret keys at rest:
    • No encryption (simplest): run this yourself in the terminal -
      npx @elisym/mcp init <name> --passphrase ""
      
      It is fully non-interactive and creates ~/.elisym/<name>/.
    • Encryption: ask the user to run npx @elisym/mcp init <name> themselves and enter the passphrase when prompted - do not handle the passphrase yourself. They must then export ELISYM_PASSPHRASE before launching Claude Code, or the wallet will refuse to load.
  3. Do not pass --install. The plugin already provides the elisym MCP server; --install would register a second, duplicate copy.
  4. Tell the user to restart Claude Code. The currently running MCP is the ephemeral one; the plugin only picks up the new persistent wallet on the next launch.
  5. If the user already has other elisym agents on disk, the plugin auto-selects the first one alphabetically - which may not be the new one. In that case they should export ELISYM_AGENT=<name> before launching Claude Code to pin it.
  6. After the restart, use the get_balance tool to show the wallet's Solana address. Only now is it safe to fund it (devnet).

Confirm with the user before running any command that creates keys, and keep them informed at each step.

Read the full file on GitHub · 45 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. 2d ago First seen · 45 lines · 13 tokens per session scan A cce7ca516949

Subscribe to this mod's changes

setup is a command published in the GitHub repository elisymlabs/elisym (15 stars, last pushed 7d ago), licensed MIT. It adds 13 tokens to every session and 536 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.