Borrowing it
Nothing to install: this file belongs to l3lackcurtains/trading-ops. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/l3lackcurtains/trading-ops/main/.claude/commands/scan-flow.mdgit clone --depth 1 https://github.com/l3lackcurtains/trading-opsWrote 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/l3lackcurtains/trading-ops/scan-flow)<a href="https://agentmods.dev/commands/l3lackcurtains/trading-ops/scan-flow"><img src="https://agentmods.dev/badge/commands/l3lackcurtains/trading-ops/scan-flow.svg" alt="Measured on agentmods" 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.00052 | $0.01583 |
| Opus 5 | $0.00026 | $0.00792 |
| Sonnet 5 | $0.00010 | $0.00317 |
| Haiku 4.5 | $0.00005 | $0.00158 |
Grade A, and why
scan-flow 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 8d 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 — 122 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Refresh flow & positioning for: $ARGUMENTS
Use this when fresh flow data dropped (ETF flows post-close, weekly COT release Tuesday afternoon, EIA inventory Wednesday, OPEX gamma rebalance) but the chart hasn't moved enough to warrant a full re-scan.
The protocol lives in guide/scan/. Read these before starting:
guide/scan/protocol.md— read-before-scan, partial-scan patternguide/scan/structure.md— Action verdict format (flow may shift triggers)- The asset-class flow doc that matches the symbol:
- Stock →
guide/scan/data.md§ ChartExchange Flow & Squeeze - Crypto →
guide/scan/crypto-flow.md - Index →
guide/scan/index-flow.md - FX →
guide/scan/fx-flow.md - Commodity →
guide/scan/commodity-flow.md
- Stock →
Steps
1. Pre-flight
- Detect asset class from symbol — stock (
scanned/stocks/), crypto (scanned/crypto/), index (scanned/indices/), FX (scanned/fx/), commodity (scanned/commodities/). - Locate
<target-folder>(scanned/<asset-class>/<SYMBOL>/). - Verify
current.mdexists. If not, tell the user to run/scan <SYMBOL>first, and stop. - Read existing
current.md— capture header, Action verdict, TL;DR, the existing flow section (so we know what to replace), and everything else. - Read
scanned/MACRO/current.md.
2. Pull flow data (asset-class-specific)
Apply EXACTLY ONE flow protocol based on Step 1's detection:
Stock — per data.md:
- ChartExchange in parallel: dark pool, max pain, short interest, FTD, borrow fee
- State "as of" dates and lag floors
Crypto — per crypto-flow.md:
- Tier A WebFetch in parallel: alternative.me F&G, CoinGecko, OKX funding/OI, Deribit options, Bitbo ETF flows, mempool.space
- Tier B chrome-devtools captures: Coinglass funding dashboard, liquidation heatmap, options max pain
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.
- 8d ago First seen · 122 lines · 52 tokens per session scan A fbf0bca14c5d
scan-flow is a command published in the GitHub repository l3lackcurtains/trading-ops (56 stars, last pushed 4mo ago), licensed MIT. It adds 52 tokens to every session and 1,583 once invoked, about $0.0003 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-30.
Other commands, from other repositories
performance
Generate a strategy performance report with key metrics.
execute-entry
Execute a new MEICAgent iron condor entry. Only invoke when the entry decision (Step 6) is yes.
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.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.