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/discover.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/discover)<a href="https://agentmods.dev/commands/l3lackcurtains/trading-ops/discover"><img src="https://agentmods.dev/badge/commands/l3lackcurtains/trading-ops/discover/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/discover"><img src="https://agentmods.dev/badge/commands/l3lackcurtains/trading-ops/discover.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.00027 | $0.00551 |
| Opus 5 | $0.00014 | $0.00275 |
| Sonnet 5 | $0.00005 | $0.00110 |
| Haiku 4.5 | $0.00003 | $0.00055 |
Grade A, and why
discover 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 9d 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.
What it actually says
Run a screener: $ARGUMENTS
Protocol in guide/discover-rules.md. Read it before starting if you haven't this session — it has the verified Finviz filter prefix reference, all preset filter sets (r1/r2/r3/r4/quality/growth/value/defense), 0-results fallback strategy, and the SCREENS folder structure.
Steps
-
Read
guide/discover-rules.mdfor the filter syntax and presets. -
Read
scanned/MACRO/current.mdto anchor the screen to the current quadrant. If MACRO is older than 7 days, warn the user and offer to run/scan-macrofirst. -
Determine preset from
$ARGUMENTS:- Bare regime tag (
r1/r2/r3/r4) → use the strict-regime preset - Theme tag (
quality/growth/value/defense) → use the named preset - Mixed (
r3-defense) → combine, document the mix - Empty → use the regime-default preset (whatever regime MACRO currently flags)
- Bare regime tag (
-
Build the Finviz screener URL per
discover-rules.mdfilter prefix reference. Validate filter codes — the doc has the verified prefixes (fa_opmarginnotfa_opermargin, etc.). A wrong prefix returns 0 silently. -
Run the screen via WebFetch on the constructed URL. Extract candidates with their filter-relevant metrics.
-
0-results fallback per
discover-rules.md§ 0-results fallback — if the strict preset returns 0 results, document the strict run, then progressively relax filters (per the documented relaxation order) and re-run. Note every relaxation step in the saved file. -
Save to
scanned/SCREENS/<YYYY-MM-DD>-<preset>.md(or<YYYY-MM-DD>.mdfor the default preset). Use the screen-file structure spec indiscover-rules.md. -
Update
scanned/INDEX.md§ Recent screens — append the new screen entry. -
Self-improvement loop per
guide/scan/style.md§ Process self-improvement — surface any process problems (broken filter codes, ambiguous instructions, missing edge cases) at the end of your reply. Wait for user consent before editing the rules.
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.
- 9d ago First seen · 32 lines · 27 tokens per session scan A 2ca30809bd08
discover is a command published in the GitHub repository l3lackcurtains/trading-ops (56 stars, last pushed 4mo ago), licensed MIT. It adds 27 tokens to every session and 551 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.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.