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/rescan.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/rescan)<a href="https://agentmods.dev/commands/l3lackcurtains/trading-ops/rescan"><img src="https://agentmods.dev/badge/commands/l3lackcurtains/trading-ops/rescan.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.00020 | $0.00673 |
| Opus 5 | $0.00010 | $0.00336 |
| Sonnet 5 | $0.00004 | $0.00135 |
| Haiku 4.5 | $0.00002 | $0.00067 |
Grade A, and why
rescan 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 — 43 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Rescan: $ARGUMENTS
The full protocol is in guide/scan/. Read protocol.md and tiers.md before starting if not loaded this session.
Steps
-
Identify target folder:
- If
$ARGUMENTSismacro/MACRO→ target =scanned/MACRO/ - Else if folder exists at
scanned/stocks/$ARGUMENTS/→ that's the target (stock) - Else if
scanned/fx/$ARGUMENTS/→ target (FX) - Else if
scanned/indices/$ARGUMENTS/orscanned/crypto/$ARGUMENTS/→ target - Else: tell the user no
current.mdexists for this ticker and stop
- If
-
Verify
current.mdexists in the target folder. If not, this isn't a rescan — tell the user to run/scan(stock),/scan-macro, or/scan <SYMBOL>first, and stop. -
Read-before-scan per
protocol.md§ Read-before-scan protocol. Address prior triggers explicitly — did the level get tested? did the catalyst fire? did our verdict track? Log to INDEX.md § Performance / audit log if relevant. -
Rotate: save existing
current.mdcontent verbatim to<target>/archive/<prior-scan-date>.md. Same-day rescan? Overwrites prior same-day archive (git history preserves the morning version). -
Prune archive per
protocol.md§ Retention policy — or runscripts/prune-archive.py <target>. -
Pull fresh data and re-run framework:
- For macro: same data pulls as
/scan-macro - For stock: same as
/scan(full 6-pillar + multi-horizon technical read + earnings if within 90d) - For FX/index/commodity/crypto: same as
/scan <SYMBOL>(Mode B — no 6-pillar/earnings) - Detect type by inspecting the prior
current.mdstructure.
- For macro: same data pulls as
-
Write new snapshot to
<target>/current.md, dated today. -
Δ marker: prepend the new TL;DR with
**Δ since last scan (YYYY-MM-DD):** <what changed>if verdict, regime, score, or key technical state changed materially. Seestructure.md§ Δ marker. -
Update
scanned/INDEX.mdpertiers.md§ Tier-change protocol — log per-horizon changes if any.
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 · 43 lines · 0 tokens per session scan A c67dcb85c705
rescan is a command published in the GitHub repository l3lackcurtains/trading-ops (56 stars, last pushed 4mo ago), licensed MIT. It adds 20 tokens to every session and 673 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-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.