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/commands/iamgoatedaf/lighter-mcp/lighter-positions)<a href="https://agentmods.dev/commands/iamgoatedaf/lighter-mcp/lighter-positions"><img src="https://agentmods.dev/badge/commands/iamgoatedaf/lighter-mcp/lighter-positions/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/commands/iamgoatedaf/lighter-mcp/lighter-positions"><img src="https://agentmods.dev/badge/commands/iamgoatedaf/lighter-mcp/lighter-positions.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.00028 | $0.00234 |
| Opus 5 | $0.00014 | $0.00117 |
| Sonnet 5 | $0.00006 | $0.00047 |
| Haiku 4.5 | $0.00003 | $0.00023 |
Grade A, and why
lighter-positions 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 10d 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.
What it actually says
/lighter-positions
Read-only. Do not modify any orders.
Steps:
- Call
lighter_account_infoto get current positions and account equity. - For each non-zero position, call
lighter_market_statsfor the matching symbol to grab the current mark/index price (one call per symbol). - For each position, compute and display:
- symbol, side (long/short), size (base), notional (USD),
- entry price, current mark, unrealized PnL (USD and %),
- approximate distance to liquidation as a percentage move (use the account margin info if available; otherwise mark this field as "unknown" — never invent a number).
- End with totals: aggregate notional and aggregate unrealized PnL.
If there are no open positions, say so in one line and stop.
Never call lighter_live_* or lighter_funds_* from this command.
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.
- 10d ago First seen · 26 lines · 28 tokens per session scan A fe248723dace
lighter-positions is a command published in the GitHub repository iamgoatedaf/lighter-mcp (1 stars, last pushed 4mo ago), licensed MIT. It adds 28 tokens to every session and 234 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-31.
Other commands, from other repositories
search-flights
Search award flight availability across airlines.
usage-report
Generate a comprehensive team usage and spending report for the current billing cycle.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.