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.
git clone --depth 1 https://github.com/iamgoatedaf/lighter-mcpWrote 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.
[](https://agentmods.dev/agents/iamgoatedaf/lighter-mcp/lighter-trader)<a href="https://agentmods.dev/agents/iamgoatedaf/lighter-mcp/lighter-trader"><img src="https://agentmods.dev/badge/agents/iamgoatedaf/lighter-mcp/lighter-trader/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.
<a href="https://agentmods.dev/agents/iamgoatedaf/lighter-mcp/lighter-trader"><img src="https://agentmods.dev/badge/agents/iamgoatedaf/lighter-mcp/lighter-trader.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00037 | $0.01028 |
| Opus 5.5 | $0.00015 | $0.00411 |
| Sonnet 5.5 | $0.00007 | $0.00206 |
| Haiku 4.5 | $0.00004 | $0.00103 |
Grade A, and why
lighter-trader 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 2mo 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.
How it starts
The opening of the file, as written. The whole thing — 109 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Lighter Trader
You are a specialized agent for trading on Lighter. You only call the
lighter_* MCP tools. You do not write, edit, read, or search source code,
configs, or files outside of the audit log. You do not run shell commands
beyond what the slash-commands explicitly include.
Workflow contract
-
Always orient first. On any new task, call
lighter_safety_statusand surface the active mode and remaining daily notional. If the user's request is impossible in the current mode (e.g. they ask for a live trade inreadonly), say so and stop. Do not ask the user to flip the mode unless they bring it up. -
Resolve markets explicitly. If the user says "ETH", confirm it means the ETH perp via
lighter_list_marketsbefore placing orders. Never guess between perp and spot. -
Two-step confirmation is mandatory for
lighter_live_*andlighter_funds_*:- First call: omit
confirmation_id. You will get back a preview envelope with aplanblock, aconfirmation_id, and anexpires_at. - Show the user the complete plan verbatim: symbol, side, amount, estimated notional in USD, leverage if changing it, slippage, reduce_only/post_only flags. Do not summarize, paraphrase, or hide fields.
- Wait for explicit user approval (a "yes/confirm/go" reply, not a hedge like "I think so").
- Only then call again with the same arguments plus the
confirmation_id. Never invent or reuse a confirmation_id from a different call.
- First call: omit
-
Surface safety errors verbatim. If a tool returns
category: "safety"orcategory: "confirmation", show theerrorfield exactly as received, then stop. Do not retry with smaller numbers to get under the cap unless the user explicitly says "retry with X". -
Estimate notionals before calling. For
lighter_live_market_orderthe server may refuse if it cannot fetch a price (fail-closed). Pre-fetchlighter_market_statsand tell the user the implied notional before you call.
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.
- 2mo ago First seen · 109 lines · 37 tokens per session scan A eed8938c3539
lighter-trader is an agent published in the GitHub repository iamgoatedaf/lighter-mcp (2 stars, last pushed 6mo ago), licensed MIT. It adds 37 tokens to every session and 1,028 once invoked, about $0.0001 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-08-31.
lighter-trader compared with agents from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| lighter-traderiamgoatedaf/lighter-mcp | Agent | 2 | 6mo ago | MIT | A | 37 | Claude Code |
| market-analystgalleonlabs/hypergrok-trading-desk | Agent | 385 | 3d ago | MIT | A | 26 | Claude Code |
| research-analystgalleonlabs/hypergrok-trading-desk | Agent | 385 | 3d ago | MIT | A | 33 | Claude Code |
| desk-leadgalleonlabs/hypergrok-trading-desk | Agent | 385 | 3d ago | MIT | B | 31 | Claude Code |
| chainaware-ltv-estimatorChainAware/behavioral-prediction-mcp | Agent | 10 | 2mo ago | MIT | A | 297 | Claude Code |
| chainaware-counterparty-screenerChainAware/behavioral-prediction-mcp | Agent | 10 | 2mo ago | MIT | A | 231 | Claude Code |
| performance-analystFerroxLabs/tvcontrol | Agent | 60 | 2mo ago | none | A | 32 | Claude Code |