pairs

A command that lists cryptocurrency trading pairs available through Alpaca's US venue, grouped by the asset used for pricing.

In plain words
What is it for?
Use it to see supported live and idle pairs and their names, symbols, and market status.
Why use it?
It separates markets such as BTC/USD, BTC/USDT, and BTC/BTC, which can have different trading activity, and distinguishes listed pairs from pairs currently without trades.

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/moshcoder/moshcode/pairs
Clone the repo
git clone --depth 1 https://github.com/moshcoder/moshcode
Per session 14 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 279 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. 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.00014 $0.00279
Opus 5 $0.00007 $0.00139
Sonnet 5 $0.00003 $0.00056
Haiku 4.5 $0.00001 $0.00028

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

Security

Grade A, and why

pairs scanned grade A with 1 finding 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 yesterday.

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.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

allowed-tools: Bash(moshcode crypto:*), Bash(curl -sS https://advis0r.com/api/crypto/:*)
plugins/crypto/commands/pairs.md · 32 lines

What it actually says

Task

List the supported pairs.

moshcode crypto assets --json

Fallback: curl -sS "https://advis0r.com/api/crypto/assets"

Reading the response

assets[] are { symbol, slug, base, quote, name, status }. slug is the URL-safe spelling (BTC-USD) used in paths; symbol is canonical (BTC/USD). status is live or idle.

Rules

  • Group by quote asset. The same coin priced in USD, USDT and BTC are three different markets with three different liquidity profiles.
  • idle means listed but not currently printing trades — it is not the same as unsupported. Show idle pairs, marked, rather than filtering them out.
  • If the user was looking for a specific coin, use /crypto:lookup <name> instead of scanning this list for them.
  • This is the coverage of one venue, not of crypto. A coin missing here is missing from Alpaca's US venue.
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. yesterday First seen · 32 lines · 14 tokens per session scan A bf5e2f21bdd6

Subscribe to this mod's changes

pairs is a command published in the GitHub repository moshcoder/moshcode (2 stars, last pushed yesterday), licensed MIT. It adds 14 tokens to every session and 279 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.