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.
npx agentmods add commands/moshcoder/moshcode/barsgit clone --depth 1 https://github.com/moshcoder/moshcodeWhat 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 | $0.00014 | $0.00383 |
| Opus 5 | $0.00007 | $0.00192 |
| Sonnet 5 | $0.00003 | $0.00077 |
| Haiku 4.5 | $0.00001 | $0.00038 |
Grade A, and why
bars 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/:*) What it actually says
Task
Pull historical bars for $ARGUMENTS.
moshcode crypto bars $ARGUMENTS --timeframe 1Day --limit 30 --json
Timeframes: 1Min, 5Min, 15Min, 1Hour, 1Day, 1Week. Add
--start/--end (ISO dates) to pin a window.
Fallback: curl -sS "https://advis0r.com/api/crypto/bars?symbol=<PAIR>&timeframe=1Day&limit=30"
Reading the response
bars is keyed by canonical symbol ("BTC/USD"), each value an ascending array
of { timestamp, open, high, low, close, volume, vwap }.
Rules
limitis upstream's page size, not a cap on what returns. The response can hold more bars than you asked for. If you show a subset, say which subset — "the 5 most recent of 17", never a silent truncation.- Bars are ascending by time. Confirm the direction before calling a move.
volumeis base-asset units on Alpaca's US venue alone, not aggregate market volume. Do not compare it to a CoinGecko or exchange-aggregate figure.- Crypto bars are calendar-based and continuous — no gaps, no sessions, no weekends. A "20-day" window here is not 20 trading sessions.
- End with the response's own
disclaimer.
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.
- yesterday First seen · 36 lines · 14 tokens per session scan A 23efc92b7b84
bars 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 383 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.
Other commands, from other repositories
opsx-propose
Propose a new change - create it and generate all artifacts in one step.
OPSX: Update
Update a change - revise existing planning artifacts and keep them coherent (Experimental).
opsx-apply
Implement tasks from an OpenSpec change (Experimental).
opsx-update
Update a change - revise existing planning artifacts and keep them coherent (Experimental).
OPSX: Apply
Implement tasks from an OpenSpec change (Experimental).
OPSX: Propose
Propose a new change - create it and generate all artifacts in one step.