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.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)<a href="https://agentmods.dev/commands/l3lackcurtains/trading-ops/scan"><img src="https://agentmods.dev/badge/commands/l3lackcurtains/trading-ops/scan/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/l3lackcurtains/trading-ops/scan"><img src="https://agentmods.dev/badge/commands/l3lackcurtains/trading-ops/scan.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.04374 |
| Opus 5.5 | $0.00015 | $0.01750 |
| Sonnet 5.5 | $0.00007 | $0.00875 |
| Haiku 4.5 | $0.00004 | $0.00437 |
Grade A, and why
scan 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 1mo 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 — 268 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Run a scan for: $ARGUMENTS
The protocol lives in guide/scan/. Read these before starting if you haven't this session:
guide/scan/protocol.md— read-before-scan, knowledge-base boundary, rescan rotation, outcome resolution logguide/scan/structure.md— folder layout, snapshot template, Action verdict format (verb + slug + ASCII ladder + trade table), INDEX.md formatguide/scan/tiers.md— coverage tiers (Pos / Swing / Day)guide/scan/scorecard.md— 6-pillar definitions and gatesguide/scan/style.md— tone, citation, scope, self-improvement loop
Plus the technical-read knowledge base (Step 6 below):
docs/volume-profile.md— POC / VAH / VAL / HVN / LVN, profile shapes, naked POCdocs/vwap.md— session / weekly / monthly / quarterly / anchored VWAP, ±σ bands
Plus the flow doc that matches the asset class (route via Step 0 below):
guide/scan/data.md— STOCK sourcing chainguide/scan/crypto-flow.md— CRYPTO flow & positioningguide/scan/index-flow.md— INDEX flow & positioning + GAMMAguide/scan/fx-flow.md— FX flow & positioning (COT-centric)guide/scan/commodity-flow.md— COMMODITY flow & positioning
If a step here ever conflicts with the guide, the guide wins. Open the fix there.
Step 0 — No-args mode: regenerate INDEX.md
If $ARGUMENTS is empty:
- Run
python3 scripts/regen_index.py— parses everycurrent.md's**Coverage tier:**line + catalyst date, regenerates the master coverage table + focus blocks + catalyst monitor inscanned/INDEX.md. - Manually verify the Coverage changes log + Performance audit log are still intact (the script doesn't overwrite those — they're append-only).
- Report what changed (added rows / tier transitions / new catalysts).
If the script fails, regenerate by hand per structure.md § INDEX.md format — walk every scanned/<asset-class>/<TICKER>/current.md for the Coverage tier line + last-scan date + score + next catalyst, and rebuild the tables.
Stop here when in no-args mode. The remaining steps apply only when scanning a specific symbol.
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.
- 1mo ago First seen · 268 lines · 37 tokens per session scan A a10deaa7b49c
scan is a command published in the GitHub repository l3lackcurtains/trading-ops (57 stars, last pushed 5mo ago), licensed MIT. It adds 37 tokens to every session and 4,374 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-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.