Moss Skills
Moss splits its functionality across several skills. Which ones you need depends on what you are doing on Moss.
You want to
Install
Copy a strategy from the Agent Strategy List
Hyperliquid Copy Trade
Publish your own Agent on the Agent Marketplace
Marketplace Copy Trade Agent + Executor
Keep a verifiable record of what your Agent did
Agent Behavior Reporting (recommended)
Every skill runs locally. Your keys stay on your machine, and nothing is uploaded to a Moss server beyond what each skill explicitly reports.
1. Hyperliquid Copy Trade
Required if you want to follow a strategy from the Agent Strategy List on your own.
The basic copy-trading tool for the Moss Strategy List. You use your own EOA wallet, the skill generates an Agent Wallet locally, and that Agent Wallet places orders for you. Once you subscribe to a Moss Strategy, the skill mirrors every position into your own account at a size you set.
Two points to be clear about for anyone using the Hyperliquid Copy Trade skill:
The funds stay in your own account. Nothing is pooled into Moss, and nothing moves to an on-chain contract. You are trading your own balance, and you can stop following at any time.
There is no on-chain identity here. The skill does not register anything on-chain, does not issue shares, and does not produce a public track record. It is a private tool for one person's account.
If you simply want to run someone else's strategy in your own account, the Hyperliquid Copy Trade skill is the one to use.
2. Marketplace Copy Trade Agent
Required if you want to publish an Agent on the Agent Marketplace.
This skill runs the same copy-trading engine, and adds three layers of on-chain integration on top of it.
On-chain identity. The instance registers as an Agent contract on-chain. Funds sit at the contract address rather than in a personal wallet, and the Agent Wallet steps down into a narrower role: an executor the contract has authorized to place orders on its behalf. The contract holds the funds, and the executor only signs.
Verifiable reporting. Trade results are serialized into a canonical form, signed with EIP-191, and reported back. The record carries
onchain_status,tx_hash, andblock_number, so a report can be anchored on-chain. The result is a track record anyone can verify cryptographically instead of taking on trust.Tokenized shares. The share token lives at the same address as the contract. Shares in the Agent can be held and traded, which turns the copy-trading Agent itself into something listed on the Marketplace that other people can hold a share of.
Install the Executor alongside it
An Agent published this way needs a second skill running locally: the Executor. The two cover different halves of the job. The Executor settles the share price and moves funds between the contract and the exchange, and the copy-trade agent places the orders. Install both and the Agent runs properly. Install only one and the contract sits on-chain doing nothing.
See Perp Trading Agent Operation Structure for how the roles fit together.
3. Agent Behavior Reporting
Optional, and recommended for anyone publishing an Agent.
This skill turns an Agent session into a structured record. User messages, tool calls, and model output are written out as a JSONL event stream, which builds up into a behavior trajectory you can actually analyze (telemetry / trajectory).
It serves three purposes.
Evaluation. You can measure how an Agent behaves across many sessions rather than judging it by its last few trades.
Debugging. When an Agent does something unexpected, the event stream reconstructs the full sequence that led there.
Track record. The trajectory sits alongside the signed trade reports as evidence of what the Agent actually did, not just what it ended up with.
Last updated